Bug 1128342 - Confusing error message when spawning VM
Summary: Confusing error message when spawning VM
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: RDO
Classification: Community
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Russell Bryant
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-09 09:41 UTC by Miroslav Suchý
Modified: 2015-03-28 18:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-28 18:54:58 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Launchpad 1437694 None None None Never

Description Miroslav Suchý 2014-08-09 09:41:13 UTC
Description of problem:
I tried to spawn VM from image bigger than 2GB and I choosed m1.tiny flavour.
I got this error:
Error: Failed to launch instance "test1": Please try again later [Error: No valid host was found. ]. 
which is quite confusing and take me some time to debug.
If you can instead write something like:
  Error: Selected VM does not have enough storage to boot from selected image.
then it would be much nicer.

Version-Release number of selected component (if applicable):
openstack-nova-compute-2014.1.1-3.el7.centos.noarch
python-django-horizon-2014.1.1-4.el7.centos.noarch

How reproducible:
deterministic

Steps to Reproduce:
1. create image bigger > 2GB
2. launch new instance and select m1.tiny
3. error stated above

Comment 1 Lars Kellogg-Stedman 2015-03-28 18:54:58 UTC
Nova should be able to communicate that error in a less opaque fashion, but this is an issue that will need to be fixed upstream.  I have opened the following upstream bug:

https://bugs.launchpad.net/nova/+bug/1437694


Note You need to log in before you can comment on or make changes to this bug.