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 1982593 - podman 3.2 - CNI-in-slirp4netns DNS gets broken when running a rootful container after running a rootless container
Summary: podman 3.2 - CNI-in-slirp4netns DNS gets broken when running a rootful contai...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta
: ---
Assignee: Jindrich Novy
QA Contact: Yuhui Jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-15 08:44 UTC by Valentin Rothberg
Modified: 2023-09-15 01:11 UTC (History)
12 users (show)

Fixed In Version: podman-3.3.0-0.13.el8 or newer
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-26 07:38:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Valentin Rothberg 2021-07-15 08:44:53 UTC
Description of problem:

CNI-in-slirp4netns DNS gets broken when running a rootful container after running a rootless container

Version-Release number of selected component (if applicable):

v3.2.2


How reproducible:

Always.

Steps to Reproduce:
1. podman network create foo
2. podman run -it --rm --net=foo alpine wget -O- example.com
3. sudo podman run -it --rm --net=foo alpine wget -O- example.com

Actual results:

wget: bad address 'example.com'


Additional info:
Reported upstream: https://github.com/containers/podman/issues/10929
Upstream PR to fix main branch: https://github.com/containers/podman/pull/10936

Once the upstream got merged, we can backport to v3.2

Comment 1 Valentin Rothberg 2021-07-15 08:47:10 UTC
Assigning to Paul who's already involved in analyzing and fixing the issue upstream.

Comment 2 Paul Holzinger 2021-07-16 08:38:06 UTC
Backport PR https://github.com/containers/podman/pull/10945 has been merged into v3.2.

Comment 13 Red Hat Bugzilla 2023-09-15 01:11:31 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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