Juno with icehouse compute service object error

Bug #1408496 reported by Sam Morrison
8
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.

Revision history for this message
Joe Gordon (jogo) wrote :

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.

Changed in nova:
importance: Undecided → Medium
status: New → Triaged
importance: Medium → High
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

Part of the problem mentioned in the mailing list is already in this bug i think:
https://bugs.launchpad.net/nova/+bug/1408498

"bug in the fixed_ip object with the embedded network object which means deletes don’t work."

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/juno)

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/167593

Changed in nova:
assignee: nobody → Sergey Nikitin (snikitin)
Changed in nova:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/juno)

Reviewed: https://review.openstack.org/167593
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b29c8e09f4e5373ab7e6ca082e7d02f4baf12562
Submitter: Jenkins
Branch: stable/juno

commit b29c8e09f4e5373ab7e6ca082e7d02f4baf12562
Author: Sergey Nikitin <email address hidden>
Date: Wed Mar 25 16:46:35 2015 +0300

    Changed target version of NovaCompute object during Service backport

    When backporting a Service object to Icehouse version the embedded
    ComputeNode object was being sent back at the wrong version.
    It happens because ComputeNode object is too new for Icehouse.
    Icehouse ComputeNode object is 1.3 not 1.4.
    http://git.openstack.org/cgit/openstack/nova/tree/nova/objects/compute_node.py?h=stable/icehouse#n27

    Closes-Bug: #1408496

    Change-Id: I33d9b29e9342b5aac2644a36bf2f4d637cc8ba53

tags: added: in-stable-juno
Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → kilo-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: kilo-rc1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.