Bug 1544611

Summary: ppc64le overcloud images need to be whole disk not partitions
Product: Red Hat OpenStack Reporter: Tony Breeds <tonyb>
Component: openstack-ironicAssignee: Tony Breeds <tonyb>
Status: CLOSED ERRATA QA Contact: Barry Donahue <bdonahue>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: bfournie, dpeacock, jschluet, mburns, sclewis, srevivo
Target Milestone: Upstream M3Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: ppc64le   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-ironic-11.1.1-0.20180827214805.65ab326.el7ost python-ironic-lib-2.14.0-0.20180810074837.344161b.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:48:46 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:
Attachments:
Description Flags
Possible work around none

Description Tony Breeds 2018-02-13 03:58:42 UTC 
ppc64le requires a prepboot partition in order to boot correctly.  Currently ironic doesn't know how to create nor manage these prep partitions.

Until this is corrected we need to generate (and use) whole disk images on ppc64le
Comment 1 Tony Breeds 2018-02-13 04:01:51 UTC 
Created attachment 1395194 [details]
Possible work around

Something like this would mean that we build whole disk images rather than single partition
Comment 2 Bob Fournier 2018-02-26 16:43:15 UTC 
Setting to RFE to reflect upstream status.
Comment 3 Tony Breeds 2018-03-07 01:46:02 UTC 
While the upstream issue is RFE we need at least to land the workaround in order to be able to ship RHOS-13 with ppc64le support.
Comment 5 Bob Fournier 2018-08-02 13:39:51 UTC 
Fixes will be in OSP-14, not OSP-13, so changing target.
Comment 12 errata-xmlrpc 2019-01-11 11:48:46 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/RHEA-2019:0045