Unhelpful message when cluster creation fails due to timeout
Bug #1533887 reported by
Chris Buccella
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sahara |
Fix Released
|
Medium
|
Mikhail |
Bug Description
When cluster creation fails due to an operation timeout, the cluster status_description is set to something not so useful:
Creating cluster failed for the following reason(s):
'Operation' timed out after 300 second(s)
This doesn't give the user any indication as to what went wrong, or where to go next for debugging. Adding the actual operation to the message would be a step in the right direction.
Changed in sahara: | |
assignee: | nobody → Chris Buccella (chris-buccella) |
Changed in sahara: | |
status: | New → In Progress |
Changed in sahara: | |
importance: | Undecided → Medium |
status: | Incomplete → Confirmed |
tags: | added: low-hanging-fruit |
Changed in sahara: | |
milestone: | none → newton-1 |
Changed in sahara: | |
assignee: | nobody → Mikhail (mlelyakin) |
Changed in sahara: | |
milestone: | newton-1 → newton-2 |
To post a comment you must log in.
This bug is > 60 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.
If the bug is still valid, then update the bug status.