Originally described in https://bugzilla.redhat.com/show_bug.cgi?id=2271761, it is not possible to trigger a GMR (Guru Meditation Report) [1] for the nova-api service in 17.1 and a backport is needed. GMR extracts debugging information from a running service such as thread and green thread stack traces.

This is impacting a high severity customer case [2] in that we are unable to obtain a GMR to aid in debugging and we expect it will continue to impact our ability to debug customer cases in the future.

The necessary patch is very small and low risk:

https://review.opendev.org/c/openstack/nova/+/810922

and backporting would be a worthwhile investment for future debugging of 17.1 deployments as 17.1 will be in Maintenance Support until September 22, 2026 [3].

We could alternatively have CEE temporarily patch a customer deployment, collect a GMR, then revert afterwards. But thinking ahead, it would be ideal to avoid having to repeatedly do that every time we need nova-api thread information for debugging.

[1] https://docs.openstack.org/nova/wallaby/reference/gmr.html
[2] https://issues.redhat.com/browse/OSPRH-13001
[3] https://access.redhat.com/support/policy/updates/openstack/platform