"nova boot" should not log an error if subsidiary commands fail

[Phil Day]

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.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/99915
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=b78c0d4f469a7e257962ede60cff472bf118e3d4
Submitter: Jenkins
Branch: master

commit b78c0d4f469a7e257962ede60cff472bf118e3d4
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:
    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
    "ResourceNotFound" error when the requested vm for which details
    have to be displayed does not exist.

    Closes-Bug: #1258488
    Change-Id: If64a087944586ef5792efe3baa62e455b9bbaa07