Improve error notification when schedule_run_instance fails
Bug #1281217 reported by
Julien Vey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Undecided
|
Julien Vey | ||
Bug Description
When trying to spawn a new instance on an OpenStack installation, and the spawn fails with an error (for instance a driver error), you get a message "No valid host was found." with an empty reason
It would help to have a more meaningful message when possible in order to diagnose the problem
This would result for instance in having a message like
Error: No valid host was found. Error from host: precise64 (node precise64): InstanceDeployF
instead of just (as it is currently)
Error: No valid host was found.
| Changed in nova: | |
| assignee: | nobody → Julien Vey (vey-julien) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on nova (master) | #2 |
| Changed in nova: | |
| status: | In Progress → Incomplete |
| Changed in nova: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/