charm nova-compute doesn't deregister the service on unit removal
Bug #1691998 reported by
Patrizio Bassi
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Fix Released
|
Low
|
Martin Kalcok |
Bug Description
Openstack is deployed with a openstack-base bundle via MAAS provider
juju add-unit nova-compute
<a new bare metal machine is deployed>
openstack and nova see the new compute node, and it's working
(nova service-list shows the new machine)
juju remove-unit nova-compute/X does remove the unit, the software and even releases the machine to maas, but does't deregister it self from nova service catalog
so you have to manually issue
nova service-list to get the id
nova service-remove <id>
it would be good to have this in the stop/destroy event
Changed in charm-nova-compute: | |
assignee: | nobody → Martin Kalcok (martin-kalcok) |
status: | Triaged → In Progress |
Changed in charm-nova-compute: | |
milestone: | none → 21.04 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
i found that even neutron- openvswitch- agent is still registered
it should be cleaned up
(now i must issue neutron agent-delete <id>)