"nova boot" should not log an error if subsidiary commands fail
Bug #1258488 reported by
Phil Day
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-novaclient |
Fix Released
|
Low
|
tcs_openstack_group |
Bug Description
The shell command "boot" does a get on the server, image, and flavor after the call to create.
If the flavor or image commands fail an error is reported, which makes it look as if the server create has failed, which is confusing to the user. Failures here should just be reflected in the details displayed, but not shows as errors as such.
Similarly a failure to get the details of server should be logged in such a way that its clear the create itself worked - maybe the request id for the create should always be printed before the server.get is attempted.
Changed in python-novaclient: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in python-novaclient: | |
assignee: | nobody → sahid (sahid-ferdjaoui) |
Changed in python-novaclient: | |
assignee: | sahid (sahid-ferdjaoui) → nobody |
Changed in python-novaclient: | |
assignee: | nobody → Akhila C (chetlapalle-akhila-b) |
Changed in python-novaclient: | |
assignee: | Akhila C (chetlapalle-akhila-b) → tcs_openstack_group (tcs-openstack-group) |
Changed in python-novaclient: | |
milestone: | none → 2.18.0 |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/99915 /git.openstack. org/cgit/ openstack/ python- novaclient/ commit/ ?id=b78c0d4f469 a7e257962ede60c ff472bf118e3d4
Committed: https:/
Submitter: Jenkins
Branch: master
commit b78c0d4f469a7e2 57962ede60cff47 2bf118e3d4
Author: Jyotsna <email address hidden>
Date: Fri Jun 13 17:23:27 2014 +0530
"nova boot" should not log an error if subsidiary commands fail
Fix: tFound" error when the requested vm for which details
Intially the cli was raising "CommadError" in case the requested
flavor or image were not present.
This error category was not approrpiate as it signifies an error
in the command syntax. When the requested resource (flavour/image)
does not exist, a ResourceNotFound error should be raised. So,
added a new error category "ResourceNotFound" to cater for this
scenario and updated the code to raise this new error.
"nova show <instance_name>" command has also been updated to raise
"ResourceNo
have to be displayed does not exist.
Closes-Bug: #1258488 f5792efe3baa62e 455b9bbaa07
Change-Id: If64a087944586e