Trying to introspect available nodes give unclear error output
Bug #1754640 reported by
Steven Hardy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
In the UI (and I guess CLI given that we use the same workflows?) any attempt to introspect available nodes gives lots of errors from the mistral action about nodes being in the wrong state.
While this is correct, there should be a clearer message - we get multiple error dialogs from the UI vs one saying "please move the node to manageable state", or perhaps just prompting to ask if you want to move the node to that state.
For new users I can imagine this being confusing, particularly since the manageable/
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → rocky-1 |
tags: | added: ui workflows |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
milestone: | stein-3 → train-1 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
Changed in tripleo: | |
milestone: | train-2 → train-3 |
To post a comment you must log in.
UI has been deprecated