destroy-unit doesn't remove node from openstack
Bug #1353612 reported by
Andreas Hasenack
This bug report is a duplicate of:
Bug #1317560: remove-unit of nova-compute does not actually remove the nova service or the neutron agent.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nova-compute (Juju Charms Collection) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I have an existing openstack deployment, deployed with the charms.
When adding a compute unit, via "juju add-unit nova-compute", it correctly becomes available in openstack as a new compute node. By default, it gets placed in the "nova" AZ even.
However, when I destroy that specific unit, it's not removed from openstack. Instead, it's still listed in the "nova" AZ but with a remark: "(Services Down)". It's still listed under "Hypervisors", "System Info", "Host Aggregates" and others.
| description: | updated |
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #1 |
Revision history for this message
| James Page (james-page) wrote | #2 |
| Changed in nova-compute (Juju Charms Collection): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
Apparently this is not possible just via the command line in openstack yet:
https:/
If that's still the case, and if we don't want to run SQL directly, we could at least disable the compute service in that node for now.