Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
doRpmCommand: rpm -e cachefilesd-0.10.2-2.el6.i686 cachefilesd-debuginfo-0.10.2-2.el6.i686
doRpmCommand-result (0): /sbin/restorecon: lstat(/var/cache/fscache) failed: No such file or directory
the issue because:
$ rpm -q --scripts -p cachefilesd-0.10.2-2.el6.x86_64.rpm
postinstall scriptlet (using /bin/sh):
/sbin/chkconfig --add cachefilesd
if [ "$1" -ge 1 ]; then
/sbin/service cachefilesd condrestart > /dev/null
fi
preuninstall scriptlet (using /bin/sh):
if [ $1 -eq 0 ]; then
/sbin/service cachefilesd stop
/sbin/chkconfig --del cachefilesd
fi
postuninstall scriptlet (using /bin/sh):
if [ $1 -eq 0 ]; then
# Fix up non-standard directory context
/sbin/restorecon -R /var/cache/fscache || :
\---> here not check if the dir is exists
fi
Version-Release number of selected component (if applicable):
cachefilesd-0.10.2-2.el6
How reproducible:
100%
Steps to Reproduce:
1. rpm all yum install cachefilesd-0.10.2-2.el6
2. rpm -e cachefilesd-0.10.2-2.el6
Actual results:
when remove package cachefilesd, user get a fail msg
Expected results:
no fail msg if success
Additional info:
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://rhn.redhat.com/errata/RHBA-2016-0975.html
Description of problem: doRpmCommand: rpm -e cachefilesd-0.10.2-2.el6.i686 cachefilesd-debuginfo-0.10.2-2.el6.i686 doRpmCommand-result (0): /sbin/restorecon: lstat(/var/cache/fscache) failed: No such file or directory the issue because: $ rpm -q --scripts -p cachefilesd-0.10.2-2.el6.x86_64.rpm postinstall scriptlet (using /bin/sh): /sbin/chkconfig --add cachefilesd if [ "$1" -ge 1 ]; then /sbin/service cachefilesd condrestart > /dev/null fi preuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then /sbin/service cachefilesd stop /sbin/chkconfig --del cachefilesd fi postuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then # Fix up non-standard directory context /sbin/restorecon -R /var/cache/fscache || : \---> here not check if the dir is exists fi Version-Release number of selected component (if applicable): cachefilesd-0.10.2-2.el6 How reproducible: 100% Steps to Reproduce: 1. rpm all yum install cachefilesd-0.10.2-2.el6 2. rpm -e cachefilesd-0.10.2-2.el6 Actual results: when remove package cachefilesd, user get a fail msg Expected results: no fail msg if success Additional info: