Hit this bug yesterday, I was unable to reset my compute node status using
`openstack segment host update $SEGMENT_UUID node01 --on_maintenance False`.
After much digging I noticed that there was still a notification with "running".
I worked around this by logging into the DB and deleting the running record from the notifications table.
Hit this bug yesterday, I was unable to reset my compute node status using
`openstack segment host update $SEGMENT_UUID node01 --on_maintenance False`.
After much digging I noticed that there was still a notification with "running".
I worked around this by logging into the DB and deleting the running record from the notifications table.