Bug 1554766

Summary:	Missing dependencies for discovery-remaster
Product:	Red Hat Satellite	Reporter:	Jakub Bittner <jbittner>
Component:	Packaging	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Sachin Ghai <sghai>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bkearney, ehelms, lzap, pcreech, rabajaj, sghai
Target Milestone:	6.4.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	foreman-discovery-image-3.5.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:17:18 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:	1596043

Description Jakub Bittner 2018-03-13 10:23:12 UTC

Description of problem:

On freshly installed Satellite 6.3 Capsule server command discovery-remaster throws error due to missing commands.

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

foreman-discovery-image-3.4.4-1.el7sat.noarch

How reproducible:

Easily.

Steps to Reproduce:
1. yum install foreman-discovery-image rubygem-smart_proxy_discovery -y
2. katello-service restart
3. discovery-remaster /usr/share/foreman-discovery-image/foreman-discovery-image-3.4.4-1.iso proxy.url=https://capsule.url.cz:9090 proxy.type=proxy

Actual results:
discovery-remaster /usr/share/foreman-discovery-image/foreman-discovery-image-3.4.4-1.iso proxy.url=https://capsule.url.cz:9090 proxy.type=proxy
which: no isohybrid in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
which: no implantisomd5 in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
Command(s) missing, install required tools
mount: /dev/loop0 is write-protected, mounting read-only
Warning: creating filesystem that does not conform to ISO-9660.
I: -input-charset not specified, using utf-8 (detected in locale settings)
Size of boot image is 4 sectors -> No emulation
Size of boot image is 10124 sectors -> No emulation
  4.37% done, estimate finish Tue Mar 13 10:10:56 2018
  8.73% done, estimate finish Tue Mar 13 10:10:56 2018
 13.10% done, estimate finish Tue Mar 13 10:10:56 2018
 17.45% done, estimate finish Tue Mar 13 10:10:56 2018
 21.82% done, estimate finish Tue Mar 13 10:10:56 2018
 26.19% done, estimate finish Tue Mar 13 10:10:56 2018
 30.55% done, estimate finish Tue Mar 13 10:10:56 2018
 34.91% done, estimate finish Tue Mar 13 10:10:56 2018
 39.28% done, estimate finish Tue Mar 13 10:10:56 2018
 43.63% done, estimate finish Tue Mar 13 10:10:56 2018
 48.00% done, estimate finish Tue Mar 13 10:10:58 2018
 52.36% done, estimate finish Tue Mar 13 10:10:57 2018
 56.73% done, estimate finish Tue Mar 13 10:10:57 2018
 61.09% done, estimate finish Tue Mar 13 10:10:57 2018
 65.46% done, estimate finish Tue Mar 13 10:10:57 2018
 69.81% done, estimate finish Tue Mar 13 10:10:57 2018
 74.18% done, estimate finish Tue Mar 13 10:10:57 2018
 78.54% done, estimate finish Tue Mar 13 10:10:57 2018
 82.91% done, estimate finish Tue Mar 13 10:10:57 2018
 87.26% done, estimate finish Tue Mar 13 10:10:57 2018
 91.63% done, estimate finish Tue Mar 13 10:10:57 2018
 95.99% done, estimate finish Tue Mar 13 10:10:57 2018
Total translation table size: 6249
Total rockridge attributes bytes: 2866
Total directory bytes: 10240
Path table size(bytes): 78
Max brk space used 22000
114603 extents written (223 MB)
/usr/bin/discovery-remaster: line 75: isohybrid: command not found
/usr/bin/discovery-remaster: line 76: implantisomd5: command not found
Created: proxy.type=proxy (BIOS/EFI compatible)


Expected results:
No errors printed out.


Additional info:
Missing packages are: syslinux, isomd5sum

Comment 7 Lukas Zapletal 2018-08-06 14:03:24 UTC

WORKAROUND:

yum -y install isohybrid implantisomd5

Comment 9 Sachin Ghai 2018-09-13 06:06:30 UTC

Verified with sat6.4.0 snap21

I ran discovery remaster on both satellite and external capsule for remastering the FDI image and didn't see the dependency issue:

~]# discovery-remaster /var/lib/libvirt/images/foreman-discovery-image-3.5.2-1.iso "fdi.pxgw=10.8.XX.XX fdi.pxdns=10.XX.XX.XX proxy.url=https://10.8.XX.XX:9090 proxy.type=proxy fdi.pxfactname1=myfact fdi.pxfactvalue1=somevalue  fdi.pxauto=1"
Extracting EFI/BOOT/BOOTX64.efi (/EFI/BOOT/BOOTX64.EFI;1)
Extracting EFI/BOOT/fonts/unicode.pf2 (/EFI/BOOT/FONTS/UNICODE.PF2;1)
Extracting EFI/BOOT/grub.cfg (/EFI/BOOT/GRUB.CFG;1)
Extracting EFI/BOOT/grubx64.efi (/EFI/BOOT/GRUBX64.EFI;1)
Extracting isolinux/boot.cat (/ISOLINUX/BOOT.CAT;1)
Extracting isolinux/efiboot.img (/ISOLINUX/EFIBOOT.IMG;1)
Extracting isolinux/initrd0.img (/ISOLINUX/INITRD0.IMG;1)
Extracting isolinux/isolinux.bin (/ISOLINUX/ISOLINUX.BIN;1)
Extracting isolinux/isolinux.cfg (/ISOLINUX/ISOLINUX.CFG;1)
Extracting isolinux/macboot.img (/ISOLINUX/MACBOOT.IMG;1)
Extracting isolinux/vesamenu.c32 (/ISOLINUX/VESAMENU.C32;1)
Extracting isolinux/vmlinuz0 (/ISOLINUX/VMLINUZ0.;1)
Extracting LiveOS/osmin.img (/LIVEOS/OSMIN.IMG;1)
Extracting LiveOS/squashfs.img (/LIVEOS/SQUASHFS.IMG;1)
Warning: creating filesystem that does not conform to ISO-9660.
Size of boot image is 4 sectors -> No emulation
Size of boot image is 0 sectors -> No emulation
Total translation table size: 6249
Total rockridge attributes bytes: 2866
Total directory bytes: 10240
Path table size(bytes): 78
Max brk space used 23000
201 extents written (0 MB)
isohybrid: /var/lib/libvirt/images/foreman-discovery-image-3.5.2-1-180913_020335.iso: boot loader does not have an isolinux.bin hybrid signature. Note that isolinux-debug.bin does not support hybrid booting
Inserting md5sum into iso image...
md5 = 0b494007c3914b11aad47fcc23547227
Inserting fragment md5sums into iso image...
fragmd5 = f8c1285a2b6cf9313ce6ed48373895b44
frags = 20
Setting supported flag to 0
Created: /var/lib/libvirt/images/foreman-discovery-image-3.5.2-1-180913_020335.iso (BIOS/EFI compatible)

Comment 10 Bryan Kearney 2018-10-16 19:17:18 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-2018:2927