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.

+++ This bug was initially created as a clone of Bug #849572 +++

Description of problem:
Strange behaviour of iptables-save. After service iptables stop command iptables-save print nothing to ouput. Then I run iptables -L and now iptables-save output three lines. I think that iptables -L is read only operation and this not may effect for iptables-save. 

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


How reproducible:
always

Steps to Reproduce:
1.service iptables stop
2.iptables-save
3.iptables -L
4.iptables-save
  
Actual results:
first iptables-save prints nothing

second iptables-save prints:
iptables-save# Generated by iptables-save v1.3.5 on Mon Aug 20 04:09:43 2012
*filter
:INPUT ACCEPT [22:1432]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [16:2896]
COMMIT
# Completed on Mon Aug 20 04:09:43 2012


Expected results:
same behaviour of both iptables-save commands 

Additional info:

iptables-save dumps all IPv4 iptables rules. After service iptables stop, all netfilter firewall mudules are unloaded. Using "iptables -L" loads the base firewall modules if they are not loaded already, this results in the standard accept policy rules.

This is expected behaviour.