Hello Uday,

Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory

When trovestack runs with dev_mode=true, guest-agent requires the environment file "/etc/trove/controller.conf", which is created by nova on boot time, but the error message above seems to say the file does not exist. https://opendev.org/openstack/trove/src/branch/master/integration/scripts/fi... I think you should make sure your DIB_CLOUD_INIT_DATASOURCES environment contains "OpenStack" when creating your image to make cloud-init create the file by using metadata service. FYI: https://docs.openstack.org/trove/latest/admin/building_guest_images.html Thanks, Hirotaka On Monday, February 6, 2023 at 11:27:27 PM GMT+9, <openstack-discuss-request@lists.openstack.org> wrote: Send openstack-discuss mailing list submissions to     openstack-discuss@lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit     https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to     openstack-discuss-request@lists.openstack.org You can reach the person managing the list at     openstack-discuss-owner@lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics:   1. [osprofiler] CI broken, looks like something related to       ChangeLog not generated (Sahid Orentino Ferdjaoui)   2. Re: Experience with VGPUs (Jonathan Rosser)   3. [largescale-sig] Next meeting: Feb 8, 9utc (!) (Thierry Carrez)   4. Stopped OpenStack Trove Guest Agent Service for Development.       (Uday Dikshit) ---------------------------------------------------------------------- Message: 1 Date: Mon, 06 Feb 2023 12:37:39 +0000 From: Sahid Orentino Ferdjaoui     <sahid.ferdjaoui@industrialdiscipline.com> To: openstack-discuss@lists.openstack.org Subject: [osprofiler] CI broken, looks like something related to     ChangeLog not generated Message-ID: <Y+D0j/GDzLNh0MsX@system76-pc.localdomain> Content-Type: text/plain; charset=utf-8 Hello, There is a change here that is fixing functional test issues on CI. But we still have an issue with ChangeLog.   https://review.opendev.org/c/openstack/osprofiler/+/840711 Looks like pbr should generate it, then we include it on history.rst. But for some reason it seems that the file is not generated or got deleted at some point. Locally that is working right. Any idea what may be the problem here?   https://zuul.opendev.org/t/openstack/build/a6df711e249c4666a1a26ca6b25d6f42 Thanks, s. ------------------------------ Message: 2 Date: Mon, 6 Feb 2023 13:15:44 +0000 From: Jonathan Rosser <jonathan.rosser@rd.bbc.co.uk> To: openstack-discuss@lists.openstack.org Subject: Re: Experience with VGPUs Message-ID: <b840ea48-f19e-0b5a-b01a-b0692059f1da@rd.bbc.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Tobias, Thankyou for posting the scripts to recreate the mdev, those are very useful and have worked OK in our environment. Managing the race conditions between the nvidia gpu manager starting, re-creating the mdev and holding off nova-compute starting until that is all complete seems quite tricky. I see the comments on https://review.opendev.org/c/openstack/nova/+/864418 and I'm also interested to know how the ordering between udev rules execution and the nvidia driver being sufficiently initialised to create mdev can be expressed. Thanks again for the scripts, Jonathan. On 17/01/2023 08:54, Tobias Urdin wrote:

Hello,

We are using vGPUs with Nova on OpenStack Xena release and we?ve had a fairly good experience integration NVIDIA A10 GPUs into our cloud.

As we see it there is some painpoints that just goes with mantaining the GPU feature.

- There is a very tight coupling of the NVIDIA driver in the guest (instance) and on the compute node that needs to ? be managed.

- Doing maintainance need more planning i.e powering off instances, NVIDIA driver on compute node needs to be ? rebuilt on hypervisor if kernel is upgraded unless you?ve implemented DKMS for that.

- Because we?ve different flavor of GPU (we split the A10 cards into different flavors for maximum utilization of ? other compute resources) we added custom traits in the Placement service to handle that, handling that with ? a script since doing anything manually related to GPUs you will get confused quickly. [1]

- Since Nova does not handle recreation of mdevs (or use the new libvirt autostart feature for mdevs) we have ? a systemd unit that executes before the nova-compute service that walks all the libvirt domains and does lookups ? in Placement to recreate the mdevs before nova-compute start. [2] [3] [4]

Best regards Tobias

DISCLAIMER: Below is provided without any warranty of actually working for you or your setup and does very specific things that we need and is only provided to give you some insight and help. Use at your own risk.

[1] https://paste.opendev.org/show/b6FdfwDHnyJXR0G3XarE/ [2] https://paste.opendev.org/show/bGtO6aIE519uysvytWv0/ [3] https://paste.opendev.org/show/bftOEIPxlpLptkosxlL6/ [4] https://paste.opendev.org/show/bOYBV6lhRON4ntQKYPkb/

------------------------------ Message: 3 Date: Mon, 6 Feb 2023 14:20:50 +0100 From: Thierry Carrez <thierry@openstack.org> To: "openstack-discuss@lists.openstack.org"     <openstack-discuss@lists.openstack.org> Subject: [largescale-sig] Next meeting: Feb 8, 9utc (!) Message-ID: <55a6e03d-3bd5-8b9d-8361-f3d54127a421@openstack.org> Content-Type: text/plain; charset=UTF-8; format=flowed Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. This is a new hour, as we decided to rotate meetings between an APAC+EU time and a EU+US time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230208T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez ------------------------------ Message: 4 Date: Mon, 6 Feb 2023 07:58:30 +0000 From: Uday Dikshit <uday.dikshit@myrealdata.in> To: "openstack-discuss@lists.openstack.org"     <openstack-discuss@lists.openstack.org> Subject: Stopped OpenStack Trove Guest Agent Service for Development. Message-ID:     <BMXPR01MB2424696CCA24F08C85CDB88D8ADA9@BMXPR01MB2424.INDPRD01.PROD.OUTLOOK.COM>     Content-Type: text/plain; charset="iso-8859-1" Hello Team We are trying to use Openstack Trove in kolla-ansible Openstack Wallaby release. We created an image using tarball as well as trovestack, we created a datastore for mysql and added version using these images. But every time we create a database instance the instance in service projects runs successfully and shows active status. But when the database instance gets stuck in build state and after the timeout it logs error in trove taskmanager of polling time out. We created a customized image with the trovestack image and configured ssh in it. Then we used this customized image to check if the guestagent was running in the instance. Here are the logs mysql-instance-1:~# journalctl -u guest-agent.service | less Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 1. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 2. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 3. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:57 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:57 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 4. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed to load environment files: No such file or directory Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed to run 'start-pre' task: No such file or directory Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Failed with result 'resources'. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Failed to start OpenStack Trove Guest Agent Service for Development. Feb 04 18:10:58 mysql-instance-1 systemd[1]: guest-agent.service: Scheduled restart job, restart counter is at 5. Feb 04 18:10:58 mysql-instance-1 systemd[1]: Stopped OpenStack Trove Guest Agent Service for Development. It will be really helpful if anybody did had any idea on running trove in kolla ansible wallaby release Thanks in advance Uday Dikshit