Red Hat Bugzilla – Bug 1145146
mkdir: cannot create directory `/var/lib/rpm-state/foreman-proxy': No such file or directory while upgrading to foreman-proxy-1.6.0.8-1.el6sat.noarch
Last modified: 2017-02-23 15:55:31 EST
+++ This bug was initially created as a clone of Bug #1141730 +++ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. run rpm -Uhv /mnt/redhat/brewroot/packages/foreman-proxy/1.6.0.30/1.el6sat/data/signed/fd431d51/noarch/foreman-proxy-1.6.0.30-1.el6sat.noarch.rpm 2. 3. Actual results: mkdir: cannot create directory `/var/lib/rpm-state/foreman-proxy': No such file or directory cp: cannot create regular file `/var/lib/rpm-state/foreman-proxy/settings.yml.orig': No such file or directory 1:foreman-proxy warning: /etc/foreman-proxy/settings.yml created as /etc/foreman-proxy/settings.yml.rpmnew now downgrading: /etc/foreman-proxy/settings.d is gone but /var/lib/rpm-state/ remained so another upgrade test is with no mkdir errors Expected results: Additional info: this might be related to the fix in https://github.com/theforeman/foreman-packaging/pull/297/commits which wasn't cherry picked to this build. running: #rpm -qp --scripts /mnt/redhat/brewroot/packages/foreman-proxy/1.6.0.30/1.el6sat/data/signed/fd431d51/noarch/foreman-proxy-1.6.0.30-1.el6sat.noarch.rpm shows the problem: test -e /var/lib/rpm-state/foreman-proxy || mkdir /var/lib/rpm-state/foreman-proxy
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Should be picked up if rebased.
Verified on: Satellite-6.1.0-RHEL-7-20150303.0 Steps to verify: [root@sat6 ~]# rpm -q foreman-proxy foreman-proxy-1.7.2.3-1.el7sat.noarch Satellite 6.1 installs foreman-proxy 1.7 instead of 1.6. I'm verifying this bug because it is not relevant anymore as the latest change was on 2014-09-22 targeting an older Satellite 6 release.
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