Comment 5 for bug 1858091

Looking at the details of the Rancher bug [1] you opened, you mentioned:

"Other details that may be helpful:

I assume, it can be fixed if API's support new version of Openstack:Train.

If I run - openstack:8774/v2.1/servers - unauthorized error / non-existent API.
If I run - openstack:8774/compute/v2.1/servers - it works. [ https://docs.openstack.org/api-ref/compute/ ]"

You're seeing a difference in the behavior based on the service URL for nova [2] -- 'openstack:8774' vs 'openstack:8774/compute'. The service URL comes from the service catalog which resides in the identity service (keystone). Whatever is calling the nova API should be extracting the service URL for nova from the identity token (from keystone) and using that instead of hard-coding a service URL.

It sounds like the application calling the nova API has hard-coded the service URL and when the Train version was deployed, a different/new service URL was populated in the service catalog for the compute service (nova).

[1] https://github.com/rancher/rancher/issues/24813
[2] https://docs.openstack.org/api-ref/compute/#service-urls