Use existing Metadef{type}NotFound Exceptions instead of MetadefRecordNotFound

[Wayne]

Currently, when metadef namespaces, objects or properties are not found by ID a general MetadefRecordNotFound exception is thrown. It is better use the existing MetadefNamespace/Object/PropertyNotFound Exceptions instead of the too general MetadefRecordNotFound exception.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/120355
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=86657d9a150ad5e0e5340c4657c0725bd6910e26
Submitter: Jenkins
Branch: master

commit 86657d9a150ad5e0e5340c4657c0725bd6910e26
Author: Wayne Okuma <email address hidden>
Date: Tue Sep 9 22:30:39 2014 -0700

    Use specific exceptions instead of the general MetadefRecordNotFound

    Currently, when metadef namespaces, objects or properties are not found
    by ID, a general MetadefRecordNotFound exception is raised. Instead,
    just use the specific MetadefNamespaceNotFound, MetadefObjectNotFound or
    MetadefPropertyNotFound exceptions.

    Change-Id: Icb6bf543015305174720f2fd950f5e4984f39798
    Closes-Bug: 1367650

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: proposed/juno
Review: https://review.openstack.org/127308

[OpenStack Infra (hudson-openstack)]

Change abandoned by Thierry Carrez (<email address hidden>) on branch: proposed/juno
Review: https://review.openstack.org/127308
Reason: 2014.2 released