nova service performs wrong update from version 15 to 9
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
We are running openstack mitaka out of clean installation (no upgrade).
All was functioning correctly until recently nova started to perform updates like this
2016-11-23 10:48:09.065 17498 INFO nova.service [req-c91ec40f-2dc2 - - - - -] Updating service version for nova-conductor on nova-tlc01.specs.de from 15 to 9
The full error log from /var/log/
2016-11-23 10:48:08.967 17499 INFO nova.service [-] Starting conductor node (version 13.1.2)
2016-11-23 10:48:09.065 17498 INFO nova.service [req-c91ec40f-2dc2- - - - - -] Updating service version for nova-conductor on nova-tlc01.specs.de from 15 to 9
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
2016-11-23 10:48:09.068 17498 ERROR oslo_service.
I checked the changes in recent versions of nova/service.py
https:/
What this means is that you are not running mitaka code everywhere. At least one service was upgraded to newton (where version 15 was introduced), it updated its service record, and then may or may not have been downgraded back. At that point, if you stop all the mitaka services, you end up with the newest service in the deployment at 15, which may then start doing things assuming no version 9 services will ever come back, which is why the version 9 services refuse to start.
So, if I were you, I would try tweaking the service records (in the services table) back to version 9 and then start all your services again (ensuring they are all on mitaka) and hope for the best. That, or upgrade to newton.