openstack node delete usability issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Brad P. Crochet |
Bug Description
I've been trying to use openstack overcloud node delete and I noticed some issues we probably want to address:
1. --stack option is mandatory. We should default this to "overcloud" the same as the deploy command? If you don't pass --stack, the command fails obscurely:
u'message': u"Failed to run action [action_
u'status': u'FAILED'}
So we probably also need to output a more meaningful error in the case where the --stack option is wrong (references a non-existent stack)
2. The command exits before the scale-down is completed. It sits for a while, then exits, but the scaledown is still running:
[stack@instack ~]$ openstack overcloud node delete --stack overcloud bc04d434-
deleting nodes [u'bc04d434-
Started Mistral Workflow tripleo.
[stack@instack ~]$ nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 8e00f89c-
| bc04d434-
| 0950c9ff-
+------
[stack@instack ~]$ heat stack-list
WARNING (shell) "heat stack-list" is deprecated, please use "openstack stack list" instead
+------
| id | stack_name | stack_status | creation_time | updated_time |
+------
| a7516e44-
3. Related to the above, there's no indication of status. We should probably poll for events and display them exactly like the deploy command does?
Changed in tripleo: | |
assignee: | nobody → Brad P. Crochet (brad-9) |
tags: | added: tripleoclient |
Changed in tripleo: | |
assignee: | Brad P. Crochet (brad-9) → Dougal Matthews (d0ugal) |
status: | Triaged → In Progress |
Changed in tripleo: | |
assignee: | Dougal Matthews (d0ugal) → Brad P. Crochet (brad-9) |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
Also the docs http:// docs.openstack. org/developer/ tripleo- docs/post_ deployment/ delete_ nodes.html say you have to pass --templates and -e options - I think this is now optional, but if not then it should be as we can do a patch update to heat which just uses the existing environment/ template etc.