The issue, it turns out, is that TripleO runs nova-api with Apache which doesn't get the nova-osapi_compute service record created in the database, which is what this code would do (but doesn't with Apache):
Running nova-api under Apache is experimental and we don't test it in our gating jobs.
So I think we should just provide a hack workaround for this in Ocata (since today is rc1) and then work on getting one of our gating jobs to run nova-api under Apache in Pike, probably the -placement- job.
The issue, it turns out, is that TripleO runs nova-api with Apache which doesn't get the nova-osapi_compute service record created in the database, which is what this code would do (but doesn't with Apache):
https:/ /github. com/openstack/ nova/blob/ ed55dcad83d5db2 fa7e43fc3d5465d f1550b554c/ nova/service. py#L139
As noted here:
https:/ /github. com/openstack/ nova/blob/ ed55dcad83d5db2 fa7e43fc3d5465d f1550b554c/ nova/wsgi/ nova-api. py#L15
Running nova-api under Apache is experimental and we don't test it in our gating jobs.
So I think we should just provide a hack workaround for this in Ocata (since today is rc1) and then work on getting one of our gating jobs to run nova-api under Apache in Pike, probably the -placement- job.