exception.NotFound is parsed wrong at the API level

[Feilong Wang]

When user updates an image with location but introduced a typo, it's expected to run into location not found exception. However, because we don't distinguish the image not found and location not found, so Glance will say the image is not found based on current design.

Failed to find image 41a997ac-e647-4b5f-b158-8e6e13875f88 to update

See https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L124 and https://github.com/openstack/glance/blob/master/glance/store/filesystem.py#L156 Though I think the issue is also existed in other backends.

[Feilong Wang (flwang)]

The root cause of this issue is that we don't support the corresponding NotFound exception for different resource type, such as image, member, location, etc.

[OpenStack Infra (hudson-openstack)]

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