Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1624215

Summary: system.product.uuid Missing on ppc64le node
Product: Red Hat OpenStack Reporter: Tony Breeds <tonyb>
Component: python-hardwareAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: bfournie, hbrock, jslagle, mburns, mlammon, slinaber
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-hardware-0.20.2-0.20190429072951.3be61d4.el7ost.noarch Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-02 20:09:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tony Breeds 2018-08-31 02:10:42 UTC
When performing extra-hardware data collection on ppc64le the system.product.uuid isn't collected, because it doesn't exist.  This key is useful for ceph deploys so collect/generate it.

Comment 2 Bob Fournier 2019-05-09 20:12:34 UTC
Per IRC Tony has indicated that this bug "needs to be closed I think.  If we're using python-hardware 0.20.1 then we should get that data for free. Yeah my RHOS-15 install the ppc64le nodes get that information"


So moving this to POST as fix is available upstream, when OSP-14 pulls in python-hardware-0.20 or later we can close this.

Comment 3 Bob Fournier 2019-06-05 20:14:56 UTC
Latest puddle for OSP-14z4 includes python-hardware-0.20.2-0.20190429072951.3be61d4.el7ost.noarch so this fix is included.

Comment 4 Bob Fournier 2019-06-05 20:16:31 UTC
Previous comment should have said 14z3 (not z4).

Comment 7 errata-xmlrpc 2019-07-02 20:09:55 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-2019:1671