Bug 2424192
| Summary: | Latest update of passt breaks rootless network when ipv6 is disabled | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Iyan <iyanmv> |
| Component: | passt | Assignee: | Stefano Brivio <sbrivio> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 42 | CC: | sbrivio |
| Target Milestone: | --- | Keywords: | Regression, Upgrades |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | passt-0^20251223.g2ba9fd5-1.fc43 passt-0^20251223.g2ba9fd5-1.fc42 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-12-31 00:50:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Iyan
2025-12-21 15:49:46 UTC
Iyan, thanks a lot for the report. (In reply to Iyan from comment #0) > My host has ipv6 disabled via kernel using `ipv6.disable=1`, and the podman > networks all have `"ipv6_enabled": false`. However, with this new version of > passt, it seems like it still tries to setup an IPv6, of course fails to do > so, and the containers are never started. Oops, of course. The buggy feature comes from https://bugs.passt.top/show_bug.cgi?id=128. I think there are two issues, actually: 1. Podman should probably tell pasta to disable IPv6, if it's disabled in the kernel. That can be done with the -4 / --ipv4-only option (which is another workaround, by the way: podman run --net=pasta:-4 ...) 2. pasta should... do something different if the kernel runs without IPv6 support or with IPv6 disabled. I'm not quite sure if we should try to enable IPv6 (unless -4 is given) and just ignore ENOTSUPP errors or similar, which looks like the robust and simple solution to me, or if we should check kernel parameters in advance. Any suggestion? I'll take care of 2. in any case. I'm not entirely sure about 1. Sorry, I meant: (In reply to Stefano Brivio from comment #1) > 1. Podman should probably tell pasta to disable IPv6, if it's disabled in > the kernel. ...if it's disabled in Podman networks with "ipv6_enabled": false. FEDORA-2025-4ef71b2b4c (passt-0^20251223.g2ba9fd5-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-4ef71b2b4c FEDORA-2025-02b4d4c380 (passt-0^20251223.g2ba9fd5-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-02b4d4c380 FEDORA-2025-02b4d4c380 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-02b4d4c380` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-02b4d4c380 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-4ef71b2b4c has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4ef71b2b4c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4ef71b2b4c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-02b4d4c380 (passt-0^20251223.g2ba9fd5-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-4ef71b2b4c (passt-0^20251223.g2ba9fd5-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |