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.
Bug 1377621 - ipsets' initscript unable to delete configuration (save empty)
Summary: ipsets' initscript unable to delete configuration (save empty)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipset
Version: 7.3
Hardware: All
OS: All
medium
low
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: Vaclav Danek
URL:
Whiteboard:
Depends On: 1136257
Blocks: 1400961
TreeView+ depends on / blocked
 
Reported: 2016-09-20 08:45 UTC by Tomas Dolezal
Modified: 2017-08-01 12:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1136257
Environment:
Last Closed: 2017-08-01 12:15:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1904 0 normal SHIPPED_LIVE ipset bug fix update 2017-08-01 16:03:41 UTC

Comment 1 Tomas Dolezal 2016-09-20 08:49:40 UTC
if there's saved configuration and ipset service was started, flushing ipset configuration followed by saving yields no results and returns exit code 0.

the quiet success of saving actually does not copy loaded configuration to saved configuration for future reloads. the end result is thus not the same as if there was any configuration present.

Comment 3 Thomas Woerner 2017-01-31 19:55:52 UTC
There is a simply solution for this:

ipset.start-stop:
-    [[ -z $(${IPSET_BIN} list -name) ]] && return 0
+    if [[ -z $(${IPSET_BIN} list -name) ]]; then
+       if [[ -f $IPSET_DATA ]]; then
+           mv $IPSET_DATA $IPSET_DATA.save && chmod 600 $IPSET_DATA.save \
+                   || return 1
+       fi
+       return 0
+    fi

Comment 7 errata-xmlrpc 2017-08-01 12:15:33 UTC
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/RHBA-2017:1904


Note You need to log in before you can comment on or make changes to this bug.