Bug 1208129

Summary:	5.4 kickstart file points to RHEL 6.5
Product:	Red Hat CloudForms Management Engine	Reporter:	John Prause <jprause>
Component:	Build	Assignee:	John Prause <jprause>
Status:	CLOSED ERRATA	QA Contact:	Milan Falešník <mfalesni>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.4.0	CC:	jhardy, jprause, mfalesni, obarenbo
Target Milestone:	GA
Target Release:	5.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-16 12:56:37 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 John Prause 2015-04-01 13:11:16 UTC

On master branch, the cfme_productization/manageiq/build/productization/kickstarts/base.ks.erb references RHEL 6.5
If we're using RHEL 6.6 on the 5.3.z builds, shouldn't the 5.4 kickstart files also use RHEL 6.6 or better?

Excerpt of the base.ks.erb:


#version=DEVEL
install
url --url=http://download.devel.redhat.com/released/RHEL-6/6.5/Server/x86_64/os/

# Update for openssl fix: https://errata.devel.redhat.com/advisory/16560
repo --name=z-stream --baseurl=http://download.eng.bos.redhat.com/devel/cfme/repos/rhel-6.5.z-x86_64-latest-pkgs/



As a point of reference, the no-cfme-vsphere.ks references the RHEL 6.6 repo.

Comment 1 John Prause 2015-04-01 17:05:05 UTC

Submitted PR with fixes for this issue.

Comment 2 John Prause 2015-04-01 17:21:59 UTC

Changes have been merged.

Comment 4 John Prause 2015-04-29 16:07:20 UTC

Yes,..that looks good.

Comment 6 Milan Falešník 2015-05-04 08:14:30 UTC

Verified in 5.4.0.0.24.20150427192818_1fd9e49

Comment 7 John Prause 2015-05-08 16:08:19 UTC

Forgot to clear the needinfo flag.
I answered Milan's question above.

Comment 10 errata-xmlrpc 2015-06-16 12:56:37 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://rhn.redhat.com/errata/RHBA-2015-1100.html