Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 is a dupe of BZ1915950. That bug has been fixed upstream by an update to v0.9.1 of the CNI plugins, which Podman will pick up in its update to v3.0.1 in the upcoming RHEL 8.4.0 release.
Going to close this as a duplicate given this.
*** This bug has been marked as a duplicate of bug 1915950 ***
Description of problem: Podman throws "Error deleting network" and "Error while removing pod" for dual-stacked networks: $ podman run --network dualstack -it --rm alpine:latest / # exit ERRO[0004] Error deleting network: running [/usr/sbin/ip6tables -t nat -D POSTROUTING -s fd05:75e:25ca:1089::4/64 -j CNI-78f6fc7a0ab09e01bc092da8 -m comment --comment name: "dualstack" id: "17882a832879b1eb68a3f5e2b30210096da6c35d537c5347a12087543409dc48" --wait]: exit status 1: iptables: Bad rule (does a matching rule exist in that chain?). ERRO[0004] Error while removing pod from CNI network "dualstack": running [/usr/sbin/ip6tables -t nat -D POSTROUTING -s fd05:75e:25ca:1089::4/64 -j CNI-78f6fc7a0ab09e01bc092da8 -m comment --comment name: "dualstack" id: "17882a832879b1eb68a3f5e2b30210096da6c35d537c5347a12087543409dc48" --wait]: exit status 1: iptables: Bad rule (does a matching rule exist in that chain?). ERRO[0004] unable to cleanup network for container 17882a832879b1eb68a3f5e2b30210096da6c35d537c5347a12087543409dc48: "error tearing down CNI namespace configuration for container 17882a832879b1eb68a3f5e2b30210096da6c35d537c5347a12087543409dc48: running [/usr/sbin/ip6tables -t nat -D POSTROUTING -s fd05:75e:25ca:1089::4/64 -j CNI-78f6fc7a0ab09e01bc092da8 -m comment --comment name: \"dualstack\" id: \"17882a832879b1eb68a3f5e2b30210096da6c35d537c5347a12087543409dc48\" --wait]: exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).\n" $ Version-Release number of selected component (if applicable): podman-2.2.1-7.module_el8.3.0+699+d61d9c41.x86_64 How reproducible: Everytime, see below Steps to Reproduce: 1. RHEL 8.3 minimal installation (including all updates) 2. dnf install podman dnsmasq -y 3. systemctl enable dnsmasq.service --now 4. cat > /etc/cni/net.d/10-dualstack-bridge.conflist <<EOF { "cniVersion": "0.4.0", "name": "dualstack", "plugins": [ { "type": "bridge", "bridge": "cni-dualstack0", "isGateway": true, "ipMasq": true, "hairpinMode": true, "ipam": { "type": "host-local", "routes": [ { "dst": "::/0" }, { "dst": "0.0.0.0/0" } ], "ranges": [ [ { "subnet": "fd05:075e:25ca:1089::/64", "gateway": "fd05:075e:25ca:1089::1" } ], [ { "subnet": "10.89.0.0/16", "gateway": "10.89.0.1" } ] ], "dns": { "nameservers" : ["fd05:075e:25ca:1089::1", "10.89.0.1"], "domain": "example.net", "search": [ "example.net" ] } } }, { "type": "portmap", "capabilities": { "portMappings": true } }, { "type": "firewall" }, { "type": "tuning" } ] } EOF 5. podman run --network dualstack -it --rm alpine:latest 6. exit # leave container 7. Get errors as mentioned above. Actual results: Podman throws "Error deleting network" and "Error while removing pod" for dual-stacked networks. Expected results: No errors thrown by podman for dual-stacked networks. Additional info: It doesn't seem to matter if there's firewalld installed and enabled vs. no firewalling at all.