Description of problem: There is a case to check what nova-api does when it failed to connect to rabbitmq. To dig the issue, we tried to get GMR by manuaal backport of the fix in gerrit[1] But it doesn't work with OSP16.2 and OSP17.1. [1] https://review.opendev.org/c/openstack/nova/+/810922 Version-Release number of selected component (if applicable): OSP16.2 and OSP17.1 How reproducible: Always Steps to Reproduce: 1. Apply the fix in https://review.opendev.org/c/openstack/nova/+/810922 2. Set the following configuration at /var/lib/config-data/puppet-generated/nova/etc/nova/nova.conf ~~~ [oslo_report] log_dir = /var/log/nova file_event_handler = /var/log/nova/gmr_trigger ~~~ 3. Run 'touch /var/log/containers/nova/gmr_trigger' 4. Run 'systemctl restart tripleo_nova_api' 5. Run 'touch /var/log/containers/nova/gmr_trigger' several times. Actual results: GMR is not recorded at any files. Expected results: GMR is recorded at a file. Additional info: The reference document is https://docs.openstack.org/nova/latest/reference/gmr.html Currently, GMR for nova_api isn't patched. However, even if the patch is applied, nova-api doesn't generate GMR. GMR is useful when we need to dig into python code while the issue because it generates thread, green threads.
The action plan for this is: - Try to backport the path to 17.1.4 or sup. - Validate if the GMR can be generated on such a platform.
At this point in time this no longer qualifies for 17.1 monthly releases criteria (critial/urgent customer bugs, or CVEs). Closing as upstream since it was done in a subsequent upstream release.