[Kolla-ansible][Yoga][Trove] Creation of instance fails
Hi, The creation of the Trove instance fails, from my debugging I found this : - The db instance is not responding on its trove interface. - The controller (trove-management) can't reach it. I have a vlan network dedicated to the Trove instances, I have created a simple VM on that network and used the same security group used by the db instance. The simple VM responds to ping and ssh connections, the Trove instance does not. I added another interface to the db instance in another network, and the instance pings and responds to ssh connections on it!!! still I don't know how to access the db instance via ssh. I don't understand. Regards.
Hi, you can ssh into the instance via the other interface and check whether the management port had got the ip address. if you can't ssh into the instances, you can try to login into the instance via web console. thanks. wodel youchi <wodel.youchi@gmail.com> 于2022年11月2日周三 01:37写道：
Hi,
The creation of the Trove instance fails, from my debugging I found this : - The db instance is not responding on its trove interface. - The controller (trove-management) can't reach it.
I have a vlan network dedicated to the Trove instances, I have created a simple VM on that network and used the same security group used by the db instance. The simple VM responds to ping and ssh connections, the Trove instance does not. I added another interface to the db instance in another network, and the instance pings and responds to ssh connections on it!!! still I don't know how to access the db instance via ssh.
I don't understand.
Regards.
Hi. Thanks for your help, I tried the master image and it is pingable and accepts ssh connection over the Trove network I couldn't wait for build of the instance to complete it was late but for now at least I can say that the yoga image has a problem. Regards On Tue, Nov 1, 2022, 18:33 wodel youchi <wodel.youchi@gmail.com> wrote:
Hi,
The creation of the Trove instance fails, from my debugging I found this : - The db instance is not responding on its trove interface. - The controller (trove-management) can't reach it.
I have a vlan network dedicated to the Trove instances, I have created a simple VM on that network and used the same security group used by the db instance. The simple VM responds to ping and ssh connections, the Trove instance does not. I added another interface to the db instance in another network, and the instance pings and responds to ssh connections on it!!! still I don't know how to access the db instance via ssh.
I don't understand.
Regards.
Hi, Using the master image did create a VM that responds on the Trove network and accepts ssh logins, but didn't complete the build of the database, I got timeout on pulling the docker image. I tested my connection with curl within the VM and it works fine. I will test with the master build image to see if this will work. Regards. Le mer. 2 nov. 2022 à 10:06, wodel youchi <wodel.youchi@gmail.com> a écrit :
Hi.
Thanks for your help, I tried the master image and it is pingable and accepts ssh connection over the Trove network I couldn't wait for build of the instance to complete it was late but for now at least I can say that the yoga image has a problem.
Regards
On Tue, Nov 1, 2022, 18:33 wodel youchi <wodel.youchi@gmail.com> wrote:
Hi,
The creation of the Trove instance fails, from my debugging I found this : - The db instance is not responding on its trove interface. - The controller (trove-management) can't reach it.
I have a vlan network dedicated to the Trove instances, I have created a simple VM on that network and used the same security group used by the db instance. The simple VM responds to ping and ssh connections, the Trove instance does not. I added another interface to the db instance in another network, and the instance pings and responds to ssh connections on it!!! still I don't know how to access the db instance via ssh.
I don't understand.
Regards.
Hi again, I have this on trove_api : /var/lib/kolla/venv/lib/python3.6/site-packages/oslo_db/sqlalchemy/enginefacade.py:342: NotSupportedWarning: Configuration option(s) ['idle_timeout'] not supported warning.NotSupportedWarning and I have this on the database instance : -- The unit guest-agent.service has entered the 'failed' state with result 'resources'. Nov 03 10:24:42 mydb01dev systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. -- Subject: A start job for unit guest-agent.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit guest-agent.service has finished with a failure. -- -- The job identifier is 1053 and the job result is failed. No much to work with to find out the why the agent doesn't start. Regards. Le jeu. 3 nov. 2022 à 10:54, wodel youchi <wodel.youchi@gmail.com> a écrit :
Hi,
Using the master image did create a VM that responds on the Trove network and accepts ssh logins, but didn't complete the build of the database, I got timeout on pulling the docker image. I tested my connection with curl within the VM and it works fine.
I will test with the master build image to see if this will work.
Regards.
Le mer. 2 nov. 2022 à 10:06, wodel youchi <wodel.youchi@gmail.com> a écrit :
Hi.
Thanks for your help, I tried the master image and it is pingable and accepts ssh connection over the Trove network I couldn't wait for build of the instance to complete it was late but for now at least I can say that the yoga image has a problem.
Regards
On Tue, Nov 1, 2022, 18:33 wodel youchi <wodel.youchi@gmail.com> wrote:
Hi,
The creation of the Trove instance fails, from my debugging I found this : - The db instance is not responding on its trove interface. - The controller (trove-management) can't reach it.
I have a vlan network dedicated to the Trove instances, I have created a simple VM on that network and used the same security group used by the db instance. The simple VM responds to ping and ssh connections, the Trove instance does not. I added another interface to the db instance in another network, and the instance pings and responds to ssh connections on it!!! still I don't know how to access the db instance via ssh.
I don't understand.
Regards.
participants (2)
-
W Ch
-
wodel youchi