[JCLOUDS-178] A 401 error should result in re-authenticating for a new token

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.2, 1.7.0
• Fix Version/s: 1.6.3, 1.7.0
• Component/s: jclouds-compute
• Assignee: Zack Shoylev
• Reporter: Zack Shoylev
• Created: 09/Jul/13 19:09
• Updated: 18/Mar/15 11:07
• Resolved: 16/Oct/13 17:57

Description

When a keystone service responds with a 401, this means the keystone token has expired. Jclouds has to then re-authenticate. Unfortunately, an extra condition in the retry was preventing this from happening.