Nova incorrectly calculates service version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Smith |
Bug Description
Nova will incorrectly calculate the service version from the database, resulting in improper upgrade decisions like automatic compute rpc version pinning.
For a dump that looks like this:
2015-10-13 23:53:15.824 | created_at updated_at deleted_at id host binary topic report_count disabled deleted disabled_reason last_seen_up forced_down version
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:39 NULL 1 devstack-
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:39 NULL 2 devstack-
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:39 NULL 3 devstack-
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:40 NULL 4 devstack-
2015-10-13 23:53:15.824 | 2015-10-13 23:42:44 2015-10-13 23:50:39 NULL 5 devstack-
Where all versions are 2, this is displayed in logs that load the compute rpcapi module:
2015-10-13 23:56:05.149 INFO nova.compute.rpcapi [req-d3601f93-
Which is clearly wrong (service_version minimum should be 2 not 0)
Changed in nova: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/234809
Review: https:/