Return reasonable error messages
Bug #1632491 reported by
Nate Potter
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Valence |
Fix Committed
|
High
|
Lin Yang | ||
Bug Description
Currently when a user asks to compose a node and the required resources aren't available, the console logs that there was an error and nothing appears in the UI. We should return an alert or some way of telling the user the reason their compose request failed (i.e. there were no systems with the requested RAM).
Revision history for this message
| Nate Potter (ntpttr) wrote | #1 |
| Changed in openstack-valence: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| Lin Yang (lin-a-yang) wrote | #2 |
| Changed in openstack-valence: | |
| assignee: | nobody → Lin Yang (lin-a-yang) |
| Changed in openstack-valence: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Lin Yang (lin-a-yang) wrote | #3 |
| Changed in openstack-valence: | |
| status: | In Progress → Fix Committed |
| Changed in openstack-valence: | |
| milestone: | none → ocata-1 |
To post a comment you must log in.
Looking at this a little deeper, it looks like the pod manager itself should be returning some better error messages. If the system with the most available memory has 8GB and I request 9, the error message returned by the podm API just says "There are no computer systems available for this allocation request", with no mention of the reason being a shortage of memory. I don't think we'll be able to fix this in Valence until the pod manager is improved here.