The only other thing I remember affecting that nova-osapi_compute service version check in Ocata was if people are running nova-api under uwsgi or mod_wsgi, as the API service version isn't set then, but running the API under uwsgi wasn't supported in Ocata anyway - so can people confirm that is not how they are running the API?
https:/ /review. openstack. org/#/c/ 427782/ was a change that made it into 15.0.0 Ocata GA.
However, looking at the code:
- we create an instance mapping record during instance create:
https:/ /github. com/openstack/ nova/blob/ 15.0.0/ nova/compute/ api.py# L1006
- assuming you make it this far (and your nova-api service version is >=15
https:/ /github. com/openstack/ nova/blob/ 15.0.0/ nova/compute/ api.py# L2271
We get the instance mapping for the instance, created above. The instance might not be in a cell at this point though.
- if the instance is not yet in a cell, we get the representation from the build request:
https:/ /github. com/openstack/ nova/blob/ 15.0.0/ nova/compute/ api.py# L2281
--
The only other thing I remember affecting that nova-osapi_compute service version check in Ocata was if people are running nova-api under uwsgi or mod_wsgi, as the API service version isn't set then, but running the API under uwsgi wasn't supported in Ocata anyway - so can people confirm that is not how they are running the API?