<div dir="ltr">Hi Hilsbos,<div><br></div><div>To access the nova instance, you need to define keypair in default section of trove.conf. </div><div><br></div><div>[Default]</div><div>...</div><div>nova_keypair = trove-key<br></div><div>...</div><div><br></div><div>Keypair (trove-key) must be created before creating a database instance.</div><div><br></div><div><span style="background-color:rgb(25,25,25);color:rgb(152,251,152);font-family:Consolas,"Courier New",Courier,Monaco,monospace;font-size:14px;font-weight:700">openstack keypair create --public-key ~/.ssh/id_rsa.pub trove-key</span> </div><div><br></div><div>Once the nova instance is deployed. you need to allow port 22 in security group of nova instance. After that use the keypair to ssh nova instance.</div><div><br></div><div>- Ammad</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 25, 2021 at 1:04 AM <<a href="mailto:DHilsbos@performair.com">DHilsbos@performair.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">All;<br>
<br>
I'm sorry for not responding earlier. The fix, I believe was to provide DNS servers to the instance.<br>
<br>
Yes, that was a head-slapping moment.<br>
<br>
I had Trove working correctly for a while, but now it's back to same basic issue; with "Dynamic backoff interval looping call 'trove.common.utils.build_polling_task.<locals>.poll_and_check' failed: oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 876.31 seconds" being reported by trove-taskmanager.<br>
<br>
To respond to Ammad's suggestion; we're using CentOS 8, so are following the instructions here: <a href="https://www.server-world.info/en/note?os=CentOS_8&p=openstack_victoria3&f=15" rel="noreferrer" target="_blank">https://www.server-world.info/en/note?os=CentOS_8&p=openstack_victoria3&f=15</a>. Note that neither the CentOS 8 version, not the Ubuntu 20.04 version mention the need for a management network.<br>
<br>
At present, I'm frustrated with the inability to access the Nova instance to observe the logs in real-time. I've tried adding commands to the end of the cloud-init file (temporarily) to set the root user password, and cloud -user password. Still can't login to the console for the Nova instance. At present, I'm resorting to "rescuing" the Nova instance with an image with a known root password, in order to read the logs after the database instances times out.<br>
<br>
Thank you,<br>
<br>
Dominic L. Hilsbos, MBA <br>
Director – Information Technology <br>
Perform Air International Inc.<br>
DHilsbos@PerformAir.com <br>
<a href="http://www.PerformAir.com" rel="noreferrer" target="_blank">www.PerformAir.com</a><br>
<br>
From: Lingxian Kong [mailto:<a href="mailto:anlin.kong@gmail.com" target="_blank">anlin.kong@gmail.com</a>] <br>
Sent: Tuesday, February 23, 2021 3:03 AM<br>
To: Ammad Syed<br>
Cc: Dominic Hilsbos; openstack-discuss<br>
Subject: Re: [ops][victoria][trove] Problems running Trove<br>
<br>
Hi Dominic,<br>
<br>
Ammad is right, you can ignore the "dumpe2fs" command error, trove-guestagent just raises the error when the data storage is initialized for the first time.<br>
<br>
The warning message "No such container: database" could also be ignored, trove-guestagent is checking if the database container is already running before creating a new one.<br>
<br>
You need to scroll down to look for the real error, maybe you can paste the trove-guestagent log so we could help you.<br>
<br>
---<br>
Lingxian Kong<br>
Senior Cloud Engineer (Catalyst Cloud)<br>
Trove PTL (OpenStack)<br>
OpenStack Cloud Provider Co-Lead (Kubernetes)<br>
<br>
<br>
On Tue, Feb 23, 2021 at 5:53 PM Ammad Syed <<a href="mailto:syedammad83@gmail.com" target="_blank">syedammad83@gmail.com</a>> wrote:<br>
Hi,<br>
<br>
I think filesystem error is ignorable as trove guest agent first check the existence of filesystem in attached block device.<br>
<br>
The second error looks like its enable to find container image in docker hub. Could you please check the name of datastore and version.<br>
<br>
Currently only mysql mariadb and postgresql are supported.<br>
<br>
Review below link this will be helpful.<br>
<br>
<a href="https://www.server-world.info/en/note?os=Ubuntu_20.04&p=openstack_victoria4&f=15" rel="noreferrer" target="_blank">https://www.server-world.info/en/note?os=Ubuntu_20.04&p=openstack_victoria4&f=15</a><br>
<br>
- Ammad<br>
<br>
On Tue, Feb 23, 2021 at 6:13 AM <<a href="mailto:DHilsbos@performair.com" target="_blank">DHilsbos@performair.com</a>> wrote:<br>
All;<br>
<br>
I've had a number of issues getting Trove to run for us, though I've worked through most of them (lots of network problems...).<br>
<br>
I now have the Nova instance starting, and it reaches out to the cluster's RabbitMQ instance.<br>
<br>
I'm getting these errors logged in /var/log/trove/trove-guestagent.log inside the Nova instance:<br>
ERROR trove.guestagent.volume '/dev/vdb' was not formatted.: oslo.concurrency.processutils.ProcessExecutionError: Unexpected error while running command.<br>
Command: sudo dumpe2fs /dev/vdb<br>
Exit code: 1<br>
Stdout: "Couldn't find valid filesystem superblock.\n"<br>
Stderror: 'dumpe2fs: Bad magic number in super-block while trying to open /dev/vdb\n'<br>
<br>
Farther down, I get this:<br>
WARNING trove.guestagent.utils.docker [-] Failed to get container database: docker.errors.NotFound: 404 Client Error: Not Found ("No such container: database")<br>
<br>
There are a number of similar errors, all indicating that it can't get the Docker files from somewhere.<br>
<br>
I'm not sure if the first is an actual issue. Wouldn't the current Trove setup expect it's data storage add-on volume to be blank initially?<br>
<br>
The second suggests that I still have a network issue, most likely routing, as the Nova instance thinks it has 2 routes to the internet, but only one works.<br>
<br>
Any thoughts would be appreciated.<br>
<br>
Dominic L. Hilsbos, MBA <br>
Director - Information Technology <br>
Perform Air International Inc.<br>
DHilsbos@PerformAir.com <br>
<a href="http://www.PerformAir.com" rel="noreferrer" target="_blank">www.PerformAir.com</a><br>
<br>
<br>
-- <br>
Regards,<br>
<br>
<br>
Syed Ammad Ali<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Regards,<div><br></div><div><br></div><div>Syed Ammad Ali</div></div>