no reauthetication in glance store

Bug #1733502 reported by Kairat Kushaev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glance_store
Fix Released
Undecided
Kairat Kushaev

Bug Description

It seems that something has changed in Keystone(but i am not 100% sure TBH) since 2015 and reauthentication stopped working for Swift driver in glance store.
The problem is in Swift driver:
get_auth_ref() returned a new auth_ref each time it was called so the will_expire_soon() call was useless since it always returned False. we need to use the cached auth_ref property.

Changed in glance-store:
assignee: nobody → Kairat Kushaev (kkushaev)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance_store (master)

Fix proposed to branch: master
Review: https://review.openstack.org/521753

Changed in glance-store:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance_store (master)

Reviewed: https://review.openstack.org/521753
Committed: https://git.openstack.org/cgit/openstack/glance_store/commit/?id=9ace679c1dae5e8f68946a46ce1dfb2926539b52
Submitter: Zuul
Branch: master

commit 9ace679c1dae5e8f68946a46ce1dfb2926539b52
Author: kairat_kushaev <email address hidden>
Date: Tue Nov 21 12:14:27 2017 +0400

    Use cached auth_ref instead of gettin a new one each time

    The commit fixes an issue in renewing connections to Swift in case
    if a given token is about to expire soon. get_auth_ref() returned
     a new auth_ref each time it was called so the will_expire_soon()
     call was useless since it always returned False. Now the cached
    auth_ref property is used instead.
    Closes-Bug:#1733502

    Change-Id: I6cb53aec6798f965cf2a120d4f676a43bca5046a

Changed in glance-store:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/glance_store 0.23.0

This issue was fixed in the openstack/glance_store 0.23.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.