Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1607701 - Rebase python-oslo-utils to 3.35.1
Rebase python-oslo-utils to 3.35.1
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-oslo-utils (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
low Severity low
: z2
: 13.0 (Queens)
Assigned To: Victor Stinner
Shai Revivo
: Rebase, RevisionTracker, Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-24 01:18 EDT by Jon Schlueter
Modified: 2018-08-29 12:34 EDT (History)
3 users (show)

See Also:
Fixed In Version: python-oslo-utils-3.35.1-1.el7ost
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-08-29 12:33:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2573 None None None 2018-08-29 12:34 EDT

  None (edit)
Description Jon Schlueter 2018-07-24 01:18:24 EDT
Rebase python-oslo-utils to 3.35.1 to pull in current version
Comment 8 Victor Stinner 2018-08-02 06:17:47 EDT
Marian Krcmarik asked me what has been added by this rebase. oslo.utils has been updated from 3.35.0 to 3.35.1. I see two significant changes:

* "Fix breaking unit tests due to iso8601 changes": "The move from iso8601===0.1.11 to iso8601===0.1.12 broke unit tests in oslo.utils." -- it just fixes an oslo.utils unit test, and it's only needed if iso8601 is updated to 0.1.12

* "Add private_key to the list of sanitized keys": change related to https://bugzilla.redhat.com/show_bug.cgi?id=1578343 but a keystone change is still needed to really test the fix with a functional test
Comment 11 errata-xmlrpc 2018-08-29 12:33:16 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2573

Note You need to log in before you can comment on or make changes to this bug.