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:

If I install openswan package, after collecting sosreport, iptables will be started even though iptables is stopped and chkconfig off before collecting the sosreport. 

Version-Release number of selected component (if applicable):

RHEL6.4

How reproducible:

Always

Steps to Reproduce:

1. Stop iptables.

# service iptables stop

2. Install openswan.

# yum install openswan

3. Collect iptables.

# sosreport

4. Check iptables status

# service iptables status

Actual results:

Iptables is started.

Expected results:

Iptables should be stop

Additional info:

Per my investigation, first we have

# cat /usr/lib/python2.6/site-packages/sos/plugins/openswan.py

self.collectExtOutput("/usr/sbin/ipsec barf")

Then, in /usr/libexec/ipsec/barf we have 

# cat /usr/libexec/ipsec/barf

if test -r /sbin/iptables-save
then
        iptables-save
        _________________________ iptables-nat
        iptables-save -t nat
        _________________________ iptables-mangle
        iptables-save -t mangle

After iptables-save -t nat, the iptables is started.

I think we should do something to stop iptables from being started after collecting sosreport.

Best regards,

Chen

This is a bug in ipsec's barf command. It should not modify system state. Please report a bug against the openswan pacakge (or move this bug to that component).

We are already intending to disable ipsec barf collection in sos due to bug 924925 (openswan bug 771612).

Marking this bug as a duplicate.  This has been fixed for 6.5

*** This bug has been marked as a duplicate of bug 954249 ***