Traced this through, and seems to be coming from the fact that iso8601 switched from using their own internal TZ info, to using Python3's TZ info. The difference in these objects end up being that the custom iso8601 one stringifies to 'UTC', while the python one stringifies to 'UTC+00:00'.
This causes problems in oslo.versionedobjects to_primative call here: https://github.com/openstack/oslo.versionedobjects/blob/master/oslo_versionedobjects/_utils.py#L28 Could be simple enough as change "tz == 'UTC'" to something like "'UTC' in tz". I will try that out locally and see how it goes. ** Also affects: oslo.versionedobjects Importance: Undecided Status: New ** Changed in: oslo.versionedobjects Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1744160 Title: Change in iso8601 1.12.0 date format breaks parsing with py35 Status in Cinder: New Status in Glance: New Status in OpenStack Identity (keystone): New Status in OpenStack Compute (nova): New Status in oslo.utils: New Status in oslo.versionedobjects: Confirmed Bug description: New package of iso8601 returns string in the format: '2012-02-14T20:53:07UTC+00:00' instead of: '2012-02-14T20:53:07Z' This is resulting in date string comparison failures and timeutils.parse_isotime errors with: ValueError: Unable to parse date string '2014-08-08T00:00:00UTC+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1744160/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
