Bug 1340544

Summary: Extlinux bootloader no longer installs by default in RHEL 6 images
Product: Red Hat OpenStack Reporter: Elise Gafford <egafford>
Component: sahara-image-elementsAssignee: Elise Gafford <egafford>
Status: CLOSED ERRATA QA Contact: Luigi Toscano <ltoscano>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 8.0 (Liberty)CC: kbasil, matt, mimccune, pkshiras, srevivo
Target Milestone: asyncKeywords: Regression, ZStream
Target Release: 8.0 (Liberty)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: sahara-image-elements-3.0.0-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 13:48:35 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 Elise Gafford 2016-05-27 19:18:45 UTC
Description of problem:

Because of a contract change in the bootloader element in DIB,
extlinux will no longer be automatically selected as a 
bootloader in the case that grub2 cannot be successfully 
installed. This breaks all generation of RHEL 6 images unless
the DIB_EXTLINUX argument is set to a true-equivalent value.

The DIB regression is being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1340530. This bug tracks the Sahara-side workaround.

Version-Release number of selected component (if applicable):


How reproducible:

100%

Steps to Reproduce:
1. Create any RHEL 6 image in DIB (using SIE or not) without
setting DIB_EXTLINUX=1.

Actual results: Bootloader fails to install.


Expected results: Extlinux is installed as per prior contract
in RHOS 8 DIB.

Comment 2 Luigi Toscano 2016-06-17 17:17:21 UTC
The sahara-image-create script can generate RHEL6-based Sahara images again.

Verified on:
sahara-image-elements-3.0.0-5.el7ost.noarch
diskimage-builder-1.13.0-1.el7ost.noarch
dib-utils-0.0.9-1.el7ost.noarch

Comment 4 errata-xmlrpc 2016-06-29 13:48:35 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-2016:1352