Re-opening because the patch for the RAX workaround [1] only handles the Unauthorized response for the keystone session client and not the plain http client, so those not using keystone are still hitting the problem.
[1] https://review.openstack.org/220192
Re-opening because the patch for the RAX workaround [1] only handles the Unauthorized response for the keystone session client and not the plain http client, so those not using keystone are still hitting the problem.
[1] https:/ /review. openstack. org/220192