Red Hat Bugzilla – Bug 1192560
Update foreman-discovery-image to 2.0
Last modified: 2017-02-23 15:31:05 EST
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.
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
Image should have been updated in both RHEL6 and RHEL7 composes now.
In latest sat6.1 beta snap6 compose2.. in rhel6 compose image is still old. This needs to be updated.
Created attachment 1001417 [details] screenshort of available old discovery image in recent snap
based on comment 9 and 10, moving to assigned state.
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!
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
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.
Created attachment 1007165 [details] foreman-disocvery-image for rhel6 repo
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 ~]# --
Created attachment 1007189 [details] issue with image in "foreman-discovery-image" rpm build for rhel66
Created attachment 1007202 [details] Not switching root: /sysroot does not seem to be an OS tree. /etc/os-release is missing
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.
(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.
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
This bug is slated to be released with Satellite 6.1.
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