handle exception for updating a bay which its stack has been deleted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
In Progress
|
Undecided
|
Unassigned |
Bug Description
After i create a bay and delete its corresponding stack manually, i update the bay:
magnum bay-update k8sbay replace node_count=2
the error message in cmd is:Traceback (most recent call last):
File "/usr/local/
, line 142, in _dispatch_and_reply
executor_
File "/usr/local/
, line 186, in _dispatch
executor_
File "/usr/local/
, line 129, in _do_dispatch
result = func(ctxt, **new_args)
File "/opt/stack/
in bay_update
raise exception.
NotSupported: Updating a bay when stack status is "DELETE_COMPLETE" is not suppo|
rted.
(HTTP 400)
i think it should be handled more friendly.
Changed in magnum: | |
milestone: | none → mitaka-1 |
Changed in magnum: | |
assignee: | nobody → space (fengzhr) |
Changed in magnum: | |
assignee: | space (fengzhr) → nobody |
Is this about the fact that this throws a long exception or because the error message isn't more explicitly stated ("Bay does not exist" or something)?