Public bug reported:
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-trusty-hpcloud-b2-5398906 nova-conductor conductor
49 0 0 NULL 2015-10-13 23:50:39 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:39 NULL
2 devstack-trusty-hpcloud-b2-5398906 nova-cert cert 49
0 0 NULL 2015-10-13 23:50:39 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:39 NULL
3 devstack-trusty-hpcloud-b2-5398906 nova-scheduler scheduler
49 0 0 NULL 2015-10-13 23:50:39 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:40 NULL
4 devstack-trusty-hpcloud-b2-5398906 nova-compute compute 49
0 0 NULL 2015-10-13 23:50:40 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:44 2015-10-13 23:50:39 NULL
5 devstack-trusty-hpcloud-b2-5398906 nova-network network 48
0 0 NULL 2015-10-13 23:50:39 0 2
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-73a2-4427-91d0-bb5964002592 None None] Automatically selected
compute RPC version 4.0 from minimum service version 0
Which is clearly wrong (service_version minimum should be 2 not 0)
** Affects: nova
Importance: Medium
Assignee: Dan Smith (danms)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1506089
Title:
Nova incorrectly calculates service version
Status in OpenStack Compute (nova):
In Progress
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-trusty-hpcloud-b2-5398906 nova-conductor conductor
49 0 0 NULL 2015-10-13 23:50:39 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:39 NULL
2 devstack-trusty-hpcloud-b2-5398906 nova-cert cert 49
0 0 NULL 2015-10-13 23:50:39 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:39 NULL
3 devstack-trusty-hpcloud-b2-5398906 nova-scheduler scheduler
49 0 0 NULL 2015-10-13 23:50:39 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:34 2015-10-13 23:50:40 NULL
4 devstack-trusty-hpcloud-b2-5398906 nova-compute compute 49
0 0 NULL 2015-10-13 23:50:40 0 2
2015-10-13 23:53:15.824 | 2015-10-13 23:42:44 2015-10-13 23:50:39 NULL
5 devstack-trusty-hpcloud-b2-5398906 nova-network network 48
0 0 NULL 2015-10-13 23:50:39 0 2
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-73a2-4427-91d0-bb5964002592 None None] Automatically selected
compute RPC version 4.0 from minimum service version 0
Which is clearly wrong (service_version minimum should be 2 not 0)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1506089/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
