Bug 1192560

Summary: Update foreman-discovery-image to 2.0
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: PackagingAssignee: Daniel Mach <dmach>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: bbuckingham, cwelton, dmach, jmontleo, mmccune, sghai
Target Milestone: UnspecifiedKeywords: 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: 2015-08-12 05:25:41 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:
Bug Depends On:    
Bug Blocks: 1193977    
Attachments:
Description Flags
screenshort of available old discovery image in recent snap
none
foreman-disocvery-image for rhel6 repo
none
issue with image in "foreman-discovery-image" rpm build for rhel66
none
Not switching root: /sysroot does not seem to be an OS tree. /etc/os-release is missing none

Description Lukas Zapletal 2015-02-13 17:10:55 UTC
Upstream changed the way the image is being built. We need to upgrade Makefile and SPEC of the foreman-discovery-image repo in dist-git.

I want to change naming conventions, the way the image is built and simplify the process.

PHASE 1: Get the ISO out of brew

I would like to ask mbridon to get the build out of brew first, then send me the commands which were used to do the build. I will change our Makefile to do that. I expect something like:

  $ ./build-livecd fdi-empty.ks
  $ koji spin-livecd \
    fdi-image-rhel_7_0 \
    $(cat root/usr/share/fdi/VERSION) \
    --release $(cat root/usr/share/fdi/RELEASE) \
    --repo=http://my.repo/1 \
    --scratch \
    my-tag-image
    x86_64 \
    fdi-image.ks

I want the name of the resulting ISO image to be fdi-image-rhel_7_0 or similar. We must be able to release fdi-image based off 7_1 or 8_0.

PHASE 2: Modify the SPEC

I can do this one easily as I do not need any special permissions in koji. I will modify the SPEC to wrap the fdi-image correctly. I want to change the way we ship the image, instead of including the ISO in the RPM I will extract just the image/kernel files.

Comment 5 Lukas Zapletal 2015-02-16 14:43:37 UTC
By the way if we are fine to add the upstream foreman-discovery-image kickstarts/shell scripts as SOURCE2, the tarballs are published by github automatically here:

https://github.com/theforeman/foreman-discovery-image/releases

The download that is relevant is:

https://github.com/theforeman/foreman-discovery-image/archive/2.1.0.tar.gz

Comment 8 Lukas Zapletal 2015-03-13 13:29:23 UTC
Image should have been updated in both RHEL6 and RHEL7 composes now.

Comment 9 Sachin Ghai 2015-03-13 15:08:53 UTC
In latest sat6.1 beta snap6 compose2.. in rhel6 compose image is still old. This needs to be updated.

Comment 10 Sachin Ghai 2015-03-13 15:10:02 UTC
Created attachment 1001417 [details]
screenshort of available old discovery image in recent snap

Comment 11 Sachin Ghai 2015-03-13 15:10:49 UTC
based on comment 9 and 10, moving to assigned state.

Comment 13 Lukas Zapletal 2015-03-19 10:02:57 UTC
Hello,

there is no rel-eng ticket for this, let me know if you need one. We've worked directly with dmach over e-mail in getting RHEL7 build since there were some changes in "distill" tool.

This is high priority for us. Thanks!

Comment 15 Mike McCune 2015-03-24 17:09:55 UTC
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
foreman-discovery-image-2.1.0-11          satellite-6.1.0-rhel-6-candidate  mbridon
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
foreman-discovery-image-2.1.0-9           satellite-6.1.0-rhel-7-candidate  tmlcoch

Comment 17 Sachin Ghai 2015-03-27 10:19:06 UTC
Verified with Sat61 beta snap8.  We have now foreman-discovery-image available in rhel6 repo. I didn't give it try yet. As soon as I discover a host with it.. will move this bz to verified state.

Comment 18 Sachin Ghai 2015-03-27 10:19:48 UTC
Created attachment 1007165 [details]
foreman-disocvery-image for rhel6 repo

Comment 19 Sachin Ghai 2015-03-27 11:43:07 UTC
So I just checked.. Looks like image has some issue.. I'm attaching the screenshot.

--
[root@hp-ms-01-c03 ~]# rpm -qa | grep discovery-image
foreman-discovery-image-2.1.0-11.el6_6sat.noarch
[root@hp-ms-01-c03 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.6 (Santiago)
[root@hp-ms-01-c03 ~]# 
--

Comment 20 Sachin Ghai 2015-03-27 11:44:39 UTC
Created attachment 1007189 [details]
issue with image in "foreman-discovery-image" rpm build for rhel66

Comment 21 Sachin Ghai 2015-03-27 11:55:22 UTC
Created attachment 1007202 [details]
Not switching root: /sysroot does not seem to be an OS tree. /etc/os-release is missing

Comment 22 Lukas Zapletal 2015-03-30 10:34:44 UTC
I have tested this build and it works fine:

https://brewweb.devel.redhat.com/buildinfo?buildID=427312

Please retag this into 6.1 RHEL6 and 7 and we are good to go.

Comment 23 Mathieu Bridon 2015-03-30 10:43:34 UTC
(In reply to Lukas Zapletal from comment #22)
> I have tested this build and it works fine:
> 
> https://brewweb.devel.redhat.com/buildinfo?buildID=427312
> 
> Please retag this into 6.1 RHEL6 and 7 and we are good to go.

To get it tagged, it needs to be added to the errata.

Comment 27 Sachin Ghai 2015-04-01 12:45:32 UTC
Verified with snap9(Satellite-6.1.0-RHEL-6-20150331.1).

Following version of discovery_image works with sat6 on rhel6.

foreman-discovery-image.noarch 0:2.1.0-13.el7sat

Comment 29 Bryan Kearney 2015-08-11 13:30:26 UTC
This bug is slated to be released with Satellite 6.1.

Comment 30 errata-xmlrpc 2015-08-12 05:25:41 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/RHSA-2015:1592