HTTP GET on an already deleted Audit returns a 500 HTTP status code

[Vincent Françoise]

When trying to retrieve an Audit which either does not exist at all or got previously deleted, we get a misleading status code. As the resource dos not exist, one would expect to have a 404 status code instead of a 500 status code as it is currently the case.

So the objective is to return a 404 NOT FOUND in this scenario. Also, the correct/specific exception should be raised, i.e. AuditNotFound.

[Taylor Peoples (tpeoples)]

I wasn't able to reproduce this, either with the CLI or with a REST call:

stack@vm:~/devstack$ watcher audit-show f4bd946f-8289-4024-ba2c-e150e786d0af
Audit %(audit)s could not be found (HTTP 404)

REST returns a 404 with the following response:

{
    "error_message": "{\"debuginfo\": null, \"faultcode\": \"Client\", \"faultstring\": \"Audit %(audit)s could not be found\"}"
}

It doesn't look like the audit ID in the exception message is being substituted in properly though.

[Vincent Françoise (vincent-francoise)]

@tpeoples: Well, just like for https://bugs.launchpad.net/watcher/+bug/1531877, the problem is not there anymore for me so since it works for you as well, I guess I can put it as released.