Log a more useful error when cinder auth isn't configured
This is similar to I18f162c4f8d1964cb4d0c184ff2149c76e1e86b4,
except all REST API interactions that hit the Cinder API use
the request user token, so configuring auth for [cinder] was
only recently added (in Queens) and is not required. However,
it is needed for certain scenarios where there is no user token,
like with periodic tasks to shutdown an instance and detach its
volumes. As such, we need to provide a more useful error message
to help an operator debug the problem if this don't have the
configuration needed for some operations.
Reviewed: https:/ /review. openstack. org/559399 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=b752717f253 f0c3eb45cc7ae55 30bc8f295b4c22
Committed: https:/
Submitter: Zuul
Branch: master
commit b752717f253f0c3 eb45cc7ae5530bc 8f295b4c22
Author: Matt Riedemann <email address hidden>
Date: Fri Apr 6 14:52:13 2018 -0400
Log a more useful error when cinder auth isn't configured
This is similar to I18f162c4f8d196 4cb4d0c184ff214 9c76e1e86b4,
except all REST API interactions that hit the Cinder API use
the request user token, so configuring auth for [cinder] was
only recently added (in Queens) and is not required. However,
it is needed for certain scenarios where there is no user token,
like with periodic tasks to shutdown an instance and detach its
volumes. As such, we need to provide a more useful error message
to help an operator debug the problem if this don't have the
configuration needed for some operations.
Change-Id: I7adaa003a86503 b711e87be671e9e f9c0e52b152
Related-Bug: #1761487