keystoneclient.auth_token property is prematurely evaluated, misses refresh on token expiry

[Eoghan Glynn]

The keystoneclient.auth_token property has in-built logic to refresh an auth token that's about to expire.

However we miss out on this functionality by prematurely evaluating the keystoneclient property upfront.

Hence if a ceilometerclient is used in a long-lived way (as it is the ceilometer alarm threshold evaluation), invocations on the client start failing with 401 after 24 hours by default (or whatever the token.expiration is configured as in keystone).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/39754
Committed: http://github.com/openstack/python-ceilometerclient/commit/1772adf0cce19de9ef151c24c482122f9d18507e
Submitter: Jenkins
Branch: master

commit 1772adf0cce19de9ef151c24c482122f9d18507e
Author: Eoghan Glynn <email address hidden>
Date: Thu Aug 1 17:07:09 2013 +0000

    Ensure keystoneclient.auth_token is re-evaluated

    Fixes bug 1207441

    Force the re-evaluation of the keystoneclient.auth_token property
    so as to avoid missing out on the in-built refresh logic when expiry
    is imminent.

    Change-Id: I8319e9e9a71e33e089fbe2fbc812d2b6c15da927