Node is not a valid node managed by this compute host

Bug #1309048 reported by Lucas Alvares Gomes
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ironic
Fix Released
High
Adam Gandelman

Bug Description

Caused by https://review.openstack.org/#/c/84214/

If a machine is enrolled with a state != power off nova cpu will throw:

NovaException: ab4b526e-8dfb-4489-85f6-fc2e75629656 is not a valid node managed by this compute host.
Removing descriptor: 6
2014-04-17 14:05:51.172 ERROR nova.openstack.common.threadgroup [-] ab4b526e-8dfb-4489-85f6-fc2e75629656 is not a valid node managed by this compute host.
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup Traceback (most recent call last):
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 117, in wait
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup x.wait()
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 49, in wait
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup return self.thread.wait()
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 168, in wait
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup return self._exit_event.wait()
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.7/site-packages/eventlet/event.py", line 116, in wait
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup return hubs.get_hub().switch()
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 187, in switch
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup return self.greenlet.switch()
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 194, in main
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup result = function(*args, **kwargs)
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/service.py", line 480, in run_service
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup service.start()
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/service.py", line 179, in start
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup self.manager.pre_start_hook()
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/compute/manager.py", line 1050, in pre_start_hook
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup self.update_available_resource(nova.context.get_admin_context())
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/compute/manager.py", line 5428, in update_available_resource
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup rt = self._get_resource_tracker(nodename)
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/compute/manager.py", line 611, in _get_resource_tracker
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup "compute host.") % nodename)
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup NovaException: ab4b526e-8dfb-4489-85f6-fc2e75629656 is not a valid node managed by this compute host.
2014-04-17 14:05:51.172 TRACE nova.openstack.common.threadgroup

Changed in ironic:
importance: Undecided → High
assignee: nobody → Lucas Alvares Gomes (lucasagomes)
Changed in ironic:
status: New → In Progress
Changed in ironic:
assignee: Lucas Alvares Gomes (lucasagomes) → Adam Gandelman (gandelman-a)
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to ironic (master)

Reviewed: https://review.openstack.org/88476
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=1f73e37cbaec1aa7c31d7b6fb4f9c3f4539c5ab9
Submitter: Jenkins
Branch: master

commit 1f73e37cbaec1aa7c31d7b6fb4f9c3f4539c5ab9
Author: Adam Gandelman <email address hidden>
Date: Thu Apr 17 17:47:26 2014 -0700

    Decouple state inspection and availability check

    The state of a node should only be considered when calculating
    resources, not when determining availability. This makes the driver
    consider any node that exists in the node inventory as available, and
    take into account its state when determining available resources. All nodes
    will be presented to Nova, but those that are in maintenence mode, have no
    power state or have an error power state will present zero resources.

    Closes-Bug: #1309048
    Change-Id: Ia78294ac5d39955dac99d3d773751e8f7538a74d

Changed in ironic:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in ironic:
milestone: none → juno-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in ironic:
milestone: juno-1 → 2014.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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