Keystone v3 expire dates cannot be parsed by radosgw

Bug #1517432 reported by György Szombathelyi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ceph (Ubuntu)
Fix Released
Medium
Unassigned
Vivid
Fix Committed
Medium
James Page
Wily
Fix Released
Medium
James Page
Xenial
Fix Released
Medium
Unassigned

Bug Description

Keystone v3 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." in the logs.
This is already fixed upstream, see
https://github.com/ceph/ceph/commit/136242b5612b8bbf260910b1678389361e86d22a

The particular version the bug is noticed: radosgw-0.94.3-0ubuntu2~cloud0

Tags: ceph
Revision history for this message
James Page (james-page) wrote :

https://github.com/ceph/ceph/commit/6119b152412ddfa2a614c1862aad52a123a4fe8e was included in 0.94.5 which is currently working through the SRU process.

Marking Fix Committed.

Changed in ceph (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Changed in ceph (Ubuntu Xenial):
status: Triaged → Fix Released
Changed in ceph (Ubuntu Wily):
status: New → Fix Committed
Changed in ceph (Ubuntu Vivid):
status: New → Fix Committed
Changed in ceph (Ubuntu Wily):
importance: Undecided → Medium
Changed in ceph (Ubuntu Vivid):
importance: Undecided → Medium
Revision history for this message
James Page (james-page) wrote :
James Page (james-page)
Changed in ceph (Ubuntu Wily):
assignee: nobody → James Page (james-page)
Changed in ceph (Ubuntu Vivid):
assignee: nobody → James Page (james-page)
James Page (james-page)
Changed in ceph (Ubuntu Wily):
status: Fix Committed → Fix Released
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.