Bug 1784640 - Ceph FSID generated by TripleO client could be more random
Summary: Ceph FSID generated by TripleO client could be more random
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: 16.1 (Train on RHEL 8.2)
Assignee: John Fulton
QA Contact: Alfredo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-17 21:35 UTC by John Fulton
Modified: 2020-07-29 07:50 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-common-11.3.3-0.20200423204446.86569f2.el8ost
Doc Type: Release Note
Doc Text:
Before this update, during Red Hat Ceph Storage (RHCS) deployment, Red Hat OpenStack Platform (RHOSP) director generated the CephClusterFSID by passing the desired FSID to ceph-ansible and used the Python uuid1() function. With this update, director uses the Python uuid4() function, which generates UUIDs more randomly.
Clone Of:
Environment:
Last Closed: 2020-07-29 07:50:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1856762 0 None None None 2019-12-17 21:40:12 UTC
OpenStack gerrit 699505 0 None MERGED Increase randomness of generated CephFSID 2020-07-29 14:08:14 UTC
OpenStack gerrit 712099 0 None MERGED Increase randomness of generated CephFSID 2020-07-29 14:08:14 UTC
Red Hat Product Errata RHBA-2020:3148 0 None None None 2020-07-29 07:50:53 UTC

Description John Fulton 2019-12-17 21:35:52 UTC 
The CephClusterFSID generated when TripleO deploys Ceph (by passing the desired FSID to ceph-ansible) uses Python's uuid1() [1]. It could be more random however and be generated by Python's uuid4().

[1] https://docs.python.org/3/library/uuid.html#uuid.uuid1
Comment 9 errata-xmlrpc 2020-07-29 07:50:33 UTC 
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-2020:3148
Note You need to log in before you can comment on or make changes to this bug.