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 2043008 - systemctl restart ipset extremely slow restoring large saved set
Summary: systemctl restart ipset extremely slow restoring large saved set
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: ipset
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.1
Assignee: Phil Sutter
QA Contact: Jiri Peska
URL:
Whiteboard:
: 2047275 (view as bug list)
Depends On: 2038818 2047275
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 13:44 UTC by Phil Sutter
Modified: 2023-02-28 08:23 UTC (History)
6 users (show)

Fixed In Version: ipset-7.11-7.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 2038818
Environment:
Last Closed: 2023-02-28 08:19:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-108961 0 None None None 2022-01-20 13:47:22 UTC
Red Hat Product Errata RHBA-2023:0947 0 None None None 2023-02-28 08:19:21 UTC

Description Phil Sutter 2022-01-20 13:44:52 UTC
+++ This bug was initially created as a clone of Bug #2038818 +++

Same problem in RHEL9, so apply same changes once verified.

Comment 1 Phil Sutter 2022-01-27 14:09:53 UTC
*** Bug 2047275 has been marked as a duplicate of this bug. ***

Comment 2 Phil Sutter 2022-01-31 15:49:59 UTC
Fix as agreed upon in the RHEL8 clone:

--- a/ipset.start-stop
+++ b/ipset.start-stop
@@ -257,7 +257,13 @@ load() {
        CLEAN_FILES="${CLEAN_FILES} ${mangled}"
        chmod 600 "${mangled}"
 
-       awk '/^(add|create) ('"${conflicts}"')/ { printf "%s ",$1; system("echo '${salt}'" $2 " | md5sum | head -c31"); $1=""; $2=""; print; next} {print}' "${merged}" > "${mangled}"
+       cat "${merged}" > "${mangled}"
+       IFS='|'
+       for set in ${conflicts}; do
+               new_name=$(echo "${salt}${set}" | md5sum | head -c31)
+               echo "s/^(add|create) $set /\1 $new_name /"
+       done | sed -i -r -f - "${mangled}"
+       unset IFS
        if ! ipset_restore "${mangled}"; then
                err "Failed to restore configured sets"
                exit 1

Comment 3 Phil Sutter 2022-01-31 16:37:26 UTC
Moving to 9.1 due to lack of QE capacity.

Comment 4 Phil Sutter 2022-08-17 15:06:52 UTC
Still not enough capacity for this, moving to 9.2.

Comment 5 Phil Sutter 2022-11-25 20:18:03 UTC
Jiri, do you have capacity to do this in RHEL9.1.z? It would auto-propagate to RHEL9.2.

Comment 15 errata-xmlrpc 2023-02-28 08:19:20 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 (ipset bug fix and enhancement 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-2023:0947


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