Datera driver sends expired token when reauthorizing itself

[Mike Perez]

The Datera driver when reauthorizing itself sends an expired token, which then is used by Datera storage itself to authorize against before accepting the login request. The expired token should be neglected when logging in.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/163583
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b5eb653bce08e7f89b41d982363f16c4f3b39f84
Submitter: Jenkins
Branch: master

commit b5eb653bce08e7f89b41d982363f16c4f3b39f84
Author: Mike Perez <email address hidden>
Date: Wed Mar 11 12:27:32 2015 -0700

    Unset auth token before trying to login to Datera

    After a token expires, the Datera driver would try to login, and pass
    along the expired token. This would fail because the receiving server
    will authorize anytime it's given an auth token, even for endpoints that
    don't require it. This change unsets the auth token when logging in, so
    it's not passed a long.

    Closes-Bug: #1430978
    Change-Id: Id445718e3e73b676e3af8005b8fdd1a028ef2b0e