nova-compute starts even if resource provider creation fails with conflict
Bug #2049903 reported by
Tobias Urdin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Undecided
|
Tobias Urdin | ||
Bug Description
if an operator has a compute node and reinstalls it but forget to do a "openstack compute service delete <id>" first (that would wipe the nova-compute service record and the resource provider in placement) the reinstalled compute node with the same hostname happily reports it's state as up even though the resource provider creation that nova-compute tried failed due to a conflict with the resource providers.
to do operators a big favor we should make nova-compute startup fail if the resource provider creation failed (like when there is a conflict)
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| Tobias Urdin (tobias-urdin) wrote | #1 |
Revision history for this message
| Amit Uniyal (auniyal) wrote | #2 |
| Changed in nova: | |
| assignee: | nobody → Tobias Urdin (tobias-urdin) |
To post a comment you must log in.
https:/