nova refuses to start if there are baremetal instances with no associated node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Unassigned | ||
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
This can happen if a deployment is interrupted at just the wrong time.
2014-01-25 06:53:38,781.781 14556 DEBUG nova.compute.
Traceback (most recent call last):
File "/usr/local/
timer()
File "/usr/local/
cb(*args, **kw)
File "/usr/local/
result = function(*args, **kwargs)
File "/opt/stack/
service.start()
File "/opt/stack/
self.
File "/opt/stack/
self.
File "/opt/stack/
self.
File "/opt/stack/
self.
File "/opt/stack/
node = _get_baremetal_
File "/opt/stack/
node = db.bm_node_
File "/opt/stack/
instance_uuid)
File "/opt/stack/
return f(*args, **kwargs)
File "/opt/stack/
raise exception.
InstanceNotFound: Instance 84c6090b-
If there is no allocated node, we can just skip that part of delete.
summary: |
- nova refuses to delete baremetal instances if there is no associated - node + nova refuses to start if there are baremetal instances with no + associated node |
description: | updated |
Changed in nova: | |
milestone: | none → icehouse-3 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-3 → 2014.1 |
We're running a monkeypatch to avoid this at the moment