Bug 2073316
Summary: | default network doesn't start | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Horák <dan> |
Component: | iptables | Assignee: | Phil Sutter <psutter> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 36 | CC: | agedosier, berrange, clalancette, crobinso, jforbes, kevin, laine, libvirt-maint, psutter, tstaudt, veillard, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-25 11:17:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 467765 |
Description
Dan Horák
2022-04-08 08:14:01 UTC
It's odd that the output of iptables -L would show the POSTROUTING chain, but yet that is what apparently fails. I tried the same command but using a non-existing chain for 1) the --insert option and 2) the --jump option, and in both cases the error was different from the one you've experienced. Possibly the iptables code that translates input into nftables is trying to autoadd the POSTROUTING chain and throws an error in spite of being successful? (that's purely a guess!) Anyway, this must be either in iptables or nftables. I'm reassigning to iptables since that's next in line after libvirt, and it can be further triaged from there. Thanks, Laine, for your review. If needed I can provide access to the system where I observe this behaviour. no change with kernel-5.18.0-0.rc3.27.fc37.s390x ------- Comment From WINTERA.com 2022-04-21 05:53 EDT------- I agree with laine that this must be either iptabels or nftables... Last year I helped debugging an issue with nftables and it turned out that a bad nft_chain_nat_ipv4 module was causing the problems in that configuration. (I have no further details, what was bad about the module) Seems the problem went away after upgrading the system to F-36, but still keeping rawhide 5.18 kernel and rawhide virt stack. |