Description of problem: On a clean CentOS 7.4 minimal, yum install ovirt-scheduler-proxy fails. Version-Release number of selected component (if applicable): 0.1.7-1.el7.centos How reproducible: 100% Steps to Reproduce: 1. provision a minimal CentOS 7.4 VM 2. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release42-pre.rpm 3. yum install ovirt-scheduler-proxy Actual results: (sorry, system was set in italian, translation: can't create directory /usr/share/ovirt-scheduler-proxy) Running transaction useradd: impossibile creare la directory /usr/share/ovirt-scheduler-proxy error: %pre(ovirt-scheduler-proxy-0.1.7-1.el7.centos.noarch) scriptlet failed, exit status 12 Error in PREIN scriptlet in rpm package ovirt-scheduler-proxy-0.1.7-1.el7.centos.noarch Expected results: No error in %pre scriptlet
I tried on the build from http://resources.ovirt.org/pub/ovirt-4.2-snapshot/rpm/el7/noarch/ovirt-release42-pre-4.2.0-0.4.rc1.el7.centos.noarch.rpm and I still see the same problem Running transaction useradd: cannot create directory /usr/share/ovirt-scheduler-proxy error: %pre(ovirt-scheduler-proxy-0.1.7-1.el7.centos.noarch) scriptlet failed, exit status 12 Error in PREIN scriptlet in rpm package ovirt-scheduler-proxy-0.1.7-1.el7.centos.noarch Verifying : ovirt-scheduler-proxy-0.1.7-1.el7.centos.noarch 1/1 Failed: ovirt-scheduler-proxy.noarch 0:0.1.7-1.el7.centos Re-run of the command solve the problem
Well since you tested exactly the same version where you found the bug.. it is kind of expected it fails.
The build created 0.1.7.0.1 for some reason. I triggered it again and got the proper 0.1.8. You check the package here: http://jenkins.ovirt.org/job/ovirt-scheduler-proxy_master_build-artifacts-fc25-x86_64/10/ I need to check with Sandro whether it will be picked up automatically or not.
0.1.8 published to ovirt-4.2-pre repo for testing.
Verified on repo http://resources.ovirt.org/pub/yum-repo/ovirt-release42-pre.rpm (ovirt-scheduler-proxy-0.1.8-1.el7.centos.noarch)
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.