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 1648429 - Name resolution fails in containers created by podman version 10.1.3-4.gitee513cc
Summary: Name resolution fails in containers created by podman version 10.1.3-4.gitee5...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: podman
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Brent Baude
QA Contact: Martin Jenner
URL:
Whiteboard:
: 1649640 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-09 17:17 UTC by dagray
Modified: 2023-09-15 01:27 UTC (History)
11 users (show)

Fixed In Version: podman-0.11.1.1-1.git594495d.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-28 08:01:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3715 0 None None None 2018-11-28 08:01:53 UTC

Description dagray 2018-11-09 17:17:51 UTC
DNS fails in podman containers after recent update to podman-0.10.1.3-4.gitee513cc.el7.x86_64. This error does not occur on podman version 0.10.1.3-1. 

Failing versions:
RPM name:
podman-0.10.1.3-4.gitee513cc.el7.x86_64

# podman --version
podman version 0.10.2-dev


Steps to Reproduce:
# podman run -it --rm alpine ping redhat.com

ping: bad address 'redhat.com'

or 

# podman run -it --rm alpine apk update

Comment 2 Matthew Heon 2018-11-09 17:26:04 UTC
I believe we've landed a fix for this upstream already. It doesn't look like it made it into the most recent 0.11.1 release, but we'll see about getting a build with the fix out quickly.

Comment 5 Joy Pu 2018-11-16 05:08:42 UTC
*** Bug 1649640 has been marked as a duplicate of this bug. ***

Comment 6 Joy Pu 2018-11-16 07:20:53 UTC
Test with podman-0.11.1.1-3.git594495d.el7.x86_64. And the version is already updated.
# podman version
Version:       0.11.1.1
Go Version:    go1.10.2
OS/Arch:       linux/amd64

So set this to verified.

Comment 8 errata-xmlrpc 2018-11-28 08:01:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3715

Comment 9 PassionApk 2022-06-20 09:21:52 UTC Comment hidden (spam)
Comment 10 Red Hat Bugzilla 2023-09-15 01:27:52 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


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