-
-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-authenticate in case of token expiry fails for Glance #148
Comments
@dhague Have you seen something like this before? |
Any opinions on how the token caching works from one of the maintainers? Are @loewenstein's thoughts from above correct? |
I don't think so, retry has been refactored to set the api path fog-openstack/lib/fog/openstack/core.rb Lines 85 to 92 in f72d2fc
fog-openstack/lib/fog/image/openstack/v2.rb Lines 129 to 135 in 4217d76
fog-openstack/lib/fog/image/openstack/v1.rb Lines 121 to 127 in 4217d76
|
Refreshing of expired tokens seems to be broken.
authenticate
from included core module. Then @path is set to a supported version by https://github.com/fog/fog-openstack/blob/master/lib/fog/openstack/image_v1.rb#L119-L124.authenticate
andretry
(fog-openstack/lib/fog/openstack/common.rb
Lines 22 to 28 in 9034252
fog-openstack/lib/fog/openstack/core.rb
Line 102 in 9034252
You can see a good overall log of the consequences in the BOSH OpenStack CPI issue cloudfoundry/bosh-openstack-cpi-release#40.
I.e. 300 multiple choices while actively waiting for the image to be ready to use (repeated image.reload & check state) in the fog-openstack consumer log.
A 401 followed by a 300 in the Glance HTTP log.
I could imagine this is a more general problem that just with Fog::Image::OpenStack. The root cause seems to be in common.rb and core.rb.
The text was updated successfully, but these errors were encountered: