Project

General

Profile

Actions

Bug #13680

closed

New keystone expire dates cannot be parsed

Added by Gyorgy Szombathelyi over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rgw
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Keystone in newer OpenStack releases (I saw it in Liberty) returns the token expiration date with microseconds, e.g. '2015-11-03T18:30:59.999999Z'. The parse_iso8601 function cannot deal with this, so using Keystone authentication always ends with "Failed to parse ISO8601 expiration date from Keystone response."

Actions #1

Updated by Yehuda Sadeh over 8 years ago

  • Priority changed from Normal to High
Actions #2

Updated by Matt Benjamin over 8 years ago

(believed to be resolved in keystone v3 change)

Actions #4

Updated by Yehuda Sadeh over 8 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF