Description of problem: In the 6.2.0 beta the discovery-remaster command isn't executable: # ls -l /usr/bin/discovery-remaster -rw-r--r-- 1 root root 2041 Apr 23 15:40 /usr/bin/discovery-remaster Version-Release number of selected component (if applicable): foreman-discovery-image-3.1.1-6.el7sat.noarch How reproducible: always Steps to Reproduce: 1. install foreman-discovery-images 2. try to run 'discovery-remaster' Actual results: won't run because its not executable Expected results: runs fine Additional info:
REL ENG: Please fix foreman-discovery-image.spec.tmpl file in foreman-discovery-image dist git. Section %files needs appropriate explicit attribute. Then we need new build for both platforms.
I moved to POST even when this wasn't acked yet, small change, expecting to have it waived.
Is there a Redmine issue, github PR or changeset associated to what needs changing here?
*** Bug 1335643 has been marked as a duplicate of this bug. ***
Eric, please see comment 2. I can do that for you, if you prefer.
Lukas, Please make the updates as you are less likely to mess them up and then switch this to MODIFIED once you have done so. Thanks
foreman-discovery-image-3.1.1-6.el7sat.noarch is still on latest snap so one can not test - move back to modified?
Yeah.. latest package is not in snap13.1. Lets keep it in assigned state then. thanks.
Verified. Version Verified: Snap 15.1 Steps to verify: [root@sat-test-rhel7 ~]# yum install foreman-discovery-image-3.1.1-11.el7sat.noarch.rpm [root@sat-test-rhel7 ~]# rpm -qa | grep discovery foreman-discovery-image-3.1.1-11.el7sat.noarch tfm-rubygem-hammer_cli_foreman_discovery-0.0.2.3-1.el7sat.noarch tfm-rubygem-foreman_discovery-5.0.0.8-1.el7sat.noarch [root@sat-test-rhel7 ~]# ls -l /usr/bin/discovery-remaster -rwxr-xr-x 1 root root 2041 Jun 6 07:08 /usr/bin/discovery-remaster [root@sat-test-rhel7 ~]#
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