nova/nova/api/metadata
Matt Riedemann a2653ac0d0 Handle InstanceNotFound when setting password via metadata
When setting an instance password via the metadata service, if the
instance is not found it results in a 500 response to the caller.

This change handles the InstanceNotFound error and returns it as
a 400. Note it's a 400 since the instance uuid is part of the POST
request body, not on the URL path so it's not a 404 response.

Change-Id: I4aa99b563e1a5a87aa3e3dfb28800f107676df92
Partial-Bug: #1696848
(cherry picked from commit c91ee68d49)
2017-11-14 11:59:58 -05:00
..
__init__.py Improve hacking rule to avoid author markers 2014-05-05 14:35:20 +02:00
base.py Handle keypair not found from metadata server using cells 2017-09-14 22:28:43 +01:00
handler.py remove log translation from nova.api.metadata 2017-03-21 07:15:54 -04:00
password.py Handle InstanceNotFound when setting password via metadata 2017-11-14 11:59:58 -05:00
vendordata.py New style vendordata support. 2016-07-26 08:15:25 -04:00
vendordata_dynamic.py remove log translation from nova.api.metadata 2017-03-21 07:15:54 -04:00
vendordata_json.py remove log translation from nova.api.metadata 2017-03-21 07:15:54 -04:00
wsgi.py Add pbr-installed wsgi application for metadata api 2017-05-02 16:58:11 +00:00