Hide Forgot
Version-Release number of selected component (if applicable): iptables-1.4.7-4.el6.x86_64 @ RHEL 6.2 beta Steps to Reproduce: # service iptables save iptables: Saving firewall rules to /etc/sysconfig/iptables:[FAILED] # echo $? 1 Notes: Enforcing SELinux (selinux-policy-3.7.19-113.el6.noarch).
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
I have found out that the failure is caused by restorecon command in the block > if [ $ret -eq 0 ]; then > mv -f $TMP_FILE $IPTABLES_DATA \ > && chmod 600 $IPTABLES_DATA \ > && restorecon $IPTABLES_DATA \ > || ret=1 > fi of save function. If I do hard exit at this place echoing the necessary variables, run "service iptables save" and run these 3 commands checking exit codes, restorecon one will exit with 1. Subsequently repeated restorecon will succeed returning 0. Therefore this bug may belong rather to policycoreutils[*]. I could not find any similar bug for this package. [*] # rpm -qf $(which restorecon) policycoreutils-2.0.83-19.15.el6.x86_64
This is a bug in restorecon. restorecon should only exit with non zero is something failed. Changing the label on a file is not a failure.
Fixed in policycoreutils-2.0.83-19.16.el6
*** Bug 741371 has been marked as a duplicate of this bug. ***
*** Bug 741555 has been marked as a duplicate of this bug. ***
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. http://rhn.redhat.com/errata/RHBA-2011-1637.html