Description of problem: Trying to discover host could not find vmlinuz0 and initrd0.img boot]# tree . ├── fdi-image ├── fdi-image-rhel_7-img -> fdi-image/initrd0.img ├── fdi-image-rhel_7-vmlinuz -> fdi-image/vmlinuz0 ├── foreman-discovery-image-3.5.1-2.iso-img ├── foreman-discovery-image-3.5.1-2.iso-vmlinuz ├── RedHat-6.9-x86_64-initrd.img ├── RedHat-6.9-x86_64-vmlinuz ├── RedHat-7.5-x86_64-initrd.img └── RedHat-7.5-x86_64-vmlinuz fdi-image-rhel_7-img and fdi-image-rhel_7-vmlinuz are symbolic links which should not. tree should be like # tree . ├── fdi-image │ ├── initrd0.img -> fdi-image-rhel_7-img │ └── vmlinuz0 -> fdi-image-rhel_7-vmlinuz ├── fdi-image-rhel_7-img ├── fdi-image-rhel_7-vmlinuz ├── foreman-discovery-image-3.5.1-2.iso-img ├── foreman-discovery-image-3.5.1-2.iso-vmlinuz ├── RedHat-6.9-x86_64-initrd.img ├── RedHat-6.9-x86_64-vmlinuz ├── RedHat-7.5-x86_64-initrd.img └── RedHat-7.5-x86_64-vmlinuz Version-Release number of selected component (if applicable): foreman-discovery-image-3.5.1-2.el7sat.noarch How reproducible: always Steps to Reproduce: 1. yum install foreman-discovery-image 2. tree Actual results: fdi-image directory is empty and initrd0-img and vmlinuz0 are symbolic links. Expected results: fdi-directory should have symbolic links to initrd0-img and vmlinuz0 and boot directory should have fdi-image-rhel_7-img and fdi-image-rhel_7-vmlinuz not symbolic links. Additional info:
Moving to GA as it was confirmed that this is not present with 3.4.4.
This was introduced with: https://bugzilla.redhat.com/show_bug.cgi?id=1578290
VERIFIED Version tested: Satellite 6.4 snap 21 foreman-discovery-image-3.5.2-1.el7sat.noarch boot]# tree . ├── fdi-image │ ├── foreman-discovery-image-3.5.2-1.iso-img │ ├── foreman-discovery-image-3.5.2-1.iso-vmlinuz │ ├── initrd0.img -> foreman-discovery-image-3.5.2-1.iso-img │ └── vmlinuz0 -> foreman-discovery-image-3.5.2-1.iso-vmlinuz ├── RedHat-6.9-x86_64-initrd.img ├── RedHat-6.9-x86_64-vmlinuz ├── RedHat-7.5-x86_64-initrd.img └── RedHat-7.5-x86_64-vmlinuz
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-2018:2928