Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1072953

Summary:	nova boot returns 0 when VM state is ERROR
Product:	Red Hat OpenStack	Reporter:	Martin Pavlásek <mpavlase>
Component:	python-novaclient	Assignee:	Ryan Hallisey <rhallise>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Pavlásek <mpavlase>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	jruzicka, ndipanov, rhallise, sgordon, xqueralt, yeylon
Target Milestone:	rc
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-27 14:39:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Pavlásek 2014-03-05 13:25:30 UTC

Description of problem:
When you run nova boot with --poll parameter and wrong flavor, status of VM is ERROR but return value of that command is 0.

Version-Release number of selected component (if applicable):
python-novaclient-2.15.0-1.el6ost.noarch

How reproducible:
Boot a VM with inpropriate flavor (too small for given image i.e.), and check return value.

Steps to Reproduce:
1. nova boot --poll ... 
2. echo $?

Actual results:
# echo $?
0

Expected results:
return value != 0


Additional info:

Comment 2 Stephen Gordon 2014-05-27 14:39:23 UTC

We should get this in the client rebase I am requesting under Bug # 1101015.