Juno with icehouse compute service object error
Bug #1408496 reported by
Sam Morrison
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Sergey Nikitin | ||
Juno |
Fix Released
|
High
|
Sergey Nikitin |
Bug Description
When running Juno with Icehouse computes on starting nova-compute you get a RuntimeError: maximum recursion depth exceeded while calling a Python object due to it trying to backport the service object.
This is caused by the Juno conductor, when it sends back the service object it includes an embedded compute node object at a version too new for Icehouse.
Changed in nova: | |
assignee: | nobody → Sergey Nikitin (snikitin) |
Changed in nova: | |
status: | Triaged → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
See http:// lists.openstack .org/pipermail/ openstack/ 2015-January/ 011092. html
I think this got in because we don't restart the icehouse nova-compute during the partial upgrade test. So code paths that are only run during nova-compute startup are not tested.