[placement] 404 responses do not cause exception logs
Prior to this change, a 404 caused by a not possible route being
requested (such as /placement/hello) would result in a proper 404
response but also a log message about an uncaught exception. This
made it appear that a 404 response is unexpected and something that
needs exceptional attention. It doesn't. This change makes sure
that 404s propagate up the stack in a clean way and are logged only
by the existing INFO log used for all requests.
Reviewed: https:/ /review. openstack. org/374955 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=1c859448055 236ffb4b6318460 9b89dd7f5cd322
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1c859448055236f fb4b63184609b89 dd7f5cd322
Author: Chris Dent <email address hidden>
Date: Thu Sep 22 16:03:21 2016 +0000
[placement] 404 responses do not cause exception logs
Prior to this change, a 404 caused by a not possible route being
requested (such as /placement/hello) would result in a proper 404
response but also a log message about an uncaught exception. This
made it appear that a 404 response is unexpected and something that
needs exceptional attention. It doesn't. This change makes sure
that 404s propagate up the stack in a clean way and are logged only
by the existing INFO log used for all requests.
Change-Id: I21f9411bd5154e ddc582d5f38891b e747de874b3
Closes-Bug: #1626489