Bug 2213280 - Podman with pasta networking fails
Summary: Podman with pasta networking fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: passt
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stefano Brivio
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-07 17:47 UTC by Gursewak Mangat
Modified: 2024-04-09 15:48 UTC (History)
2 users (show)

Fixed In Version: passt-0^20230625.g32660ce-1.fc39
Clone Of:
Environment:
Last Closed: 2024-04-09 15:48:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gursewak Mangat 2023-06-07 17:47:30 UTC
Description of problem:
With the latest passt version, 

Version-Release number of selected component (if applicable):
passt-0^20230509.g96f8d55-1.fc39
passt-0^20230509.g96f8d55-1.fc38

How reproducible:
Everytime

Steps to Reproduce:
1. Using latest passt packages, run a simple test to run `podman run -i --net=pasta:-g,8.8.8.8 registry.fedoraproject.org/fedora:38`
2. Verify the 8.8.8.8 got set as the gateway. No /sbin/ip so just use /proc/net/route
cat /proc/net/route | grep 08080808

Actual results:
Empty as the gateway doesn't get set now.

Expected results:
+ cat /proc/net/route
+ grep 08080808
ens7	00000000	08080808	0003	0	0	0	00000000	0	0	0 

Additional info:
The failure is seen in both FC39 and FC38 versions. 
Upstream test: https://github.com/coreos/fedora-coreos-config/blob/testing-devel/tests/kola/podman/rootless-pasta-networking

Comment 1 Stefano Brivio 2023-06-26 19:20:13 UTC
Fixed upstream by: https://passt.top/passt/commit/?id=d034fb698f2312c02642c539881b1c1e965fc8fe

included in update passt-0^20230625.g32660ce-1.fc39

Comment 2 Fedora Release Engineering 2023-08-16 07:14:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 3 Timothée Ravier 2024-04-09 15:48:03 UTC
This should be fixed now.


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