Bug 1287728

Summary:	discovery_remaster script needs to be part of discovery image rpm or ISO
Product:	Red Hat Satellite	Reporter:	Sachin Ghai <sghai>
Component:	Discovery Image	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Sachin Ghai <sghai>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.5	CC:	bbuckingham, dmoessne, mmccune, tspeetje
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:20:29 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 Sachin Ghai 2015-12-02 14:37:23 UTC

Description of problem:
we use discovery_remaster script to regenerate an ISO with extra kernel options to perform unattended discovery. This should be part of discovery image ISO

Version-Release number of selected component (if applicable):
Sat 6.1.5 compose2(Satellite-6.1.0-RHEL-7-20151125.0)
discovery image: foreman-discovery-image-3.0.5-2.iso


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Mike McCune 2015-12-04 05:54:17 UTC

moving to 6.2

Comment 6 Sachin Ghai 2016-03-16 07:54:55 UTC

Verified with foreman-discovery-image from brew, discovery-remaster script is part of discovery image rpm. 

[root@cloud~]# rpm -qpl foreman-discovery-image-3.1.1-1.el7sat.noarch.rpm
/usr/bin/discovery-remaster
/usr/share/foreman-discovery-image
/usr/share/foreman-discovery-image/foreman-discovery-image-3.1.1-1.iso

Comment 7 Sachin Ghai 2016-03-29 05:46:12 UTC

Verified with foreman-discovery-image rpm from brew having version:

foreman-discovery-image-3.1.1-1.el7sat.noarch.rpm 

Moving this to verified.

Comment 8 Bryan Kearney 2016-07-27 11:20:29 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:1501