Red Hat Bugzilla – Bug 895588
RFE: Improve granularity of "NoValidHost" error.
Last modified: 2016-04-26 12:49:57 EDT
Description of problem:
It appears that the NoValidHost error can occur for a variety of reasons:
- No hosts are available at all.
- No hosts with appropriate CPU(s) available.
- No hosts with required RAM available.
- No hosts with required disk available.
- All of the above?
Users who have experience with other compute solutions, particularly more traditional virtualization solutions, expect the error returned in these situations to be more granular and attempt to pin down *why* no host was considered valid.
Upstream blueprint exists for this, good progress is being made toward getting this merged for grizzly: https://blueprints.launchpad.net/nova/+spec/instance-actions
@rbryant: The upstream blueprint is targeted for G-3. Is this a candidate for backport or too invasive/risky?
It requires a db migration, so I don't think it's a candidate for being backported. I've bumped this to 3.0.
Russell, this is done, right?
*** This bug has been marked as a duplicate of bug 891051 ***