Need more log info for "Instance could not be found" error.

[Venkatesh Sampath]

Rarely, when looking up for the details of an 'instance_id' we get to see the following error. But the instance pertaining to the instance_id is still available and active.

call: GET /${project_id}/servers/${instance_id}
HTTP exception thrown: Instance could not be found (404)

Apart from the above, there is not enough information to traceback what exactly caused the 404. Hence some log message with traceback can help us identify the root cause.

This bug is to add more log messages with traceback for more information.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/72637

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/74294

[Tracy Jones (tjones-i)]

this has not been touched in a long time and the patches are abandoned. Please set back to in progress if you start to work on it

[Takahiro Shida (shida)]

This bug is not progress for long time. It should be close, I think

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/153474

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/153474
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=291b4a31c77f597387231f3d217116bb4f468e10
Submitter: Jenkins
Branch: master

commit 291b4a31c77f597387231f3d217116bb4f468e10
Author: Amandeep <email address hidden>
Date: Tue Mar 3 14:14:13 2015 +0530

    Add more log info around 'not found' error

    Currently log message on nova api does not
    have enough info to debug this problem.

    Now, with this patch we included more log
    messages to print more info.

    Change-Id: I73d80500ebbbe3f896658037e104be15024658ec
    Closes-Bug: #1278849