Hi, Thank you for your support. As per your advice, it will help me solve that issue. I am currently deploying Trove using Kolla Ansible 2023.1, following the guide provided here: https://satishdotpatel.github.io/trove-dbaas-openstack/ . Despite adhering closely to the instructions, I am facing an issue where the Trove instance ends up in an error state. trove-guestagent.conf [DEFAULT] transport_url = rabbit://openstack:USI0SmaT7lPF7MJCxHPZ4alm8wiyxoihssD1VlnA@192.168.1.101:5672,openstack:USI0SmaT7lPF7MJCxHPZ4alm8wiyxoihssD1VlnA@192.168.1.102:5672,openstack:USI0SmaT7lPF7MJCxHPZ4alm8wiyxoihssD1VlnA@192.168.1.103:5672// control_exchange = trove root_grant = ALL root_grant_option = True debug = False Here are the details of my configuration and the steps I have taken for troubleshooting: Configuration: guest_info.conf [DEFAULT] guest_id=54be201a-bf4b-4235-8e55-1020aa09dedc datastore_manager=mysql datastore_version=5.7.29 tenant_id=xxxxxxx instance_rpc_encr_key=xxxxxxxx Troubleshooting Steps: Docker Status Check: root@test:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f698ee14d928 mysql:5.7.29 "docker-entrypoint.s…" 18 minutes ago Up 18 minutes 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp database Telnet Connection: root@openstack-02:~# telnet 192.168.50.78 3306 Trying 192.168.50.78... Connected to 192.168.50.78. Escape character is '^]'. J 5.7.29p+C5 }0^k[zH3mysql_native_password Syslog: Jul 20 19:21:25 test guest-agent[651]: 2024-07-20 19:21:25.476 651 WARNING trove.guestagent.datastore.mysql_common.service [None req-a03ff3dd-5a8f-4fd4-80d5-76e31fa16dd0 - - - - - -] Failed to run docker command, error: Running command error: b"mysql: [Warning] Using a password on the command line interface can be insecure.\nERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)\n": Exception: Running command error: b"mysql: [Warning] Using a password on the command line interface can be insecure.\nERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)\n" /var/run/mysqld is not there Jul 20 19:22:10 test guest-agent[651]: 2024-07-20 19:22:10.316 651 ERROR trove.guestagent.datastore.service [None req-a03ff3dd-5a8f-4fd4-80d5-76e31fa16dd0 - - - - - -] Timeout while waiting for database status to change. Expected state healthy, current state is running Issues Observed: The MySQL container is running, and I can connect to the database via telnet. However, the guest agent logs indicate issues with running Docker commands and connecting to the MySQL server via the socket. Request: I am seeking advice on additional troubleshooting steps or configuration changes that might resolve these issues. Any insights or recommendations from the community would be greatly appreciated. Thank you for your support. ---- On Thu, 18 Jul 2024 13:10:36 +0530 chunyang wu <wchy1001@gmail.com> wrote --- Hi: Image Not Found: I followed the steps it downloads the required packages and it creates the image directory. However, the trove image is not present in the specified path $HOME/images. ---------------- Did you build the image via trovestack ? Could you provide more logs from the output of the trovestack command? It seems like you failed to build the image. ERROR oslo.messaging._drivers.impl_rabbit [-] Failed to declare consumer for topic 'guestagent.01a5cdd0-df3c-4f61-817f-114b530a1bb3': Queue.declare: (406) PRECONDITION_FAIL -------------- I don't know how did you deployment the rabbitmq. but this error seems to be caused by the setting of the 'oslo_messaging_rabbit' in the guest-agent.conf. could you check whether this opt was the same with the opt in the trove.conf which was generated by Kolla-ansible? AFAIK, For the 2023.1 brach, we don't need to set `[oslo_messaging_rabbit] heartbeat_in_pthread = false amqp_durable_queues = true rabbit_quorum_queue = true` in the guest-agent. These options were added in the later branch. as per: https://github.com/openstack/kolla-ansible/blob/stable/2023.1/ansible/roles/... agent[802]: 2024-07-01 09:24:13.831 802 ERROR trove.guestagent.volume [-] Volume '/dev/vdb' was not formatted.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. --------------------- this is a common message. it doesn't matter. Thamanna Farhath <mailto:thamanna.f@zybisys.com> 于2024年7月17日周三 18:07写道：
Dear OpenStack Community,
I am currently working with OpenStack Kolla Ansible 2023.1
1.setting up Trove instances as per the documentation https://docs.openstack.org/trove/2023.1/admin/building_guest_images.html Despite following the steps outlined, I am encountering some issues.
Image Not Found: I followed the steps it downloads the required packages and it creates the image directory. However, the trove image is not present in the specified path $HOME/images.
2.I have also referred to https://satishdotpatel.github.io/trove-dbaas-openstack/ and followed each step, but below issue persists. Error with Messaging and Volume Configuration: While creating a Trove instance, I encountered the following errors:
ERROR oslo.messaging._drivers.impl_rabbit [-] Failed to declare consumer for topic 'guestagent.01a5cdd0-df3c-4f61-817f-114b530a1bb3': Queue.declare: (406) PRECONDITION_FAILED - inequivalent arg 'x-queue-type' for queue 'guestagent.01a5cdd0-df3c-4f61-817f-114b530a1bb3' in vhost '/': received the value 'quorum' of type 'longstr' but current is none guest-agent[802]: 2024-07-01 09:24:13.831 802 ERROR trove.guestagent.volume [-] Volume '/dev/vdb' was not formatted.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command.
Steps Taken:
Created and configured images as per the OpenStack documentation. Ensured that all Trove-related configurations are properly set up. Verified RabbitMQ configurations to avoid direct configurations and used Trove’s trove-guestagent configuration for managing RabbitMQ settings.
/etc/kolla/config/trove.conf
[DEFAULT] management_networks = ee2a2a81-178c-4d79-867b-8baf53ec236d nova_keypair = trove-ssh-key management_security_groups = 451e4b4a-58b4-4e9f-84a8-5bdb21e34cd5
/etc/kolla/config/trove-guestagent.conf
[DEFAULT] transport_url = rabbit://openstack:<RABBITMQ_PASSWORD>@192.168.8.14:5672,openstack:<RABBITMQ_PASSWORD>@192.168.8.15:5672,openstack:<RABBITMQ_PASSWORD>@192.168.8.16:5672// control_exchange = trove root_grant = ALL root_grant_option = True debug = False [oslo_messaging_rabbit] heartbeat_in_pthread = false amqp_durable_queues = true rabbit_quorum_queue = true
Request for Assistance:
Are there any other recommended methods to build the Trove guest image if the documented steps do not work?
Is there a known core issue related to the errors I am encountering with oslo.messaging and trove.guestagent.volume?
What specific configurations or logs should I check to resolve these errors?
Any additional steps or best practices for setting up Trove instances with Kolla Ansible?
Thank you in advance for your help. Any insights or suggestions to resolve these issues would be greatly appreciated.
________________________________ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.
E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."
Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."