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 1649563 - no network access when trying to ping from container
Summary: no network access when trying to ping from container
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: podman
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Brent Baude
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-13 21:25 UTC by Micah Abbott
Modified: 2018-11-28 08:01 UTC (History)
9 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 Micah Abbott 2018-11-13 21:25:31 UTC 
Downstream version of https://github.com/containers/libpod/issues/1752


The next version of `podman` that is in testing has the same problem as described in the upstream issue.

# rpm-ostree status
State: idle; auto updates disabled
Deployments:
● ostree://custom:rhel-atomic-host/7/x86_64/standard
                   Version: 7.6.1 (2018-11-13 17:46:27)
                    Commit: 8b42e385c425c65b793547c7e59e772c0e8e7c04c874cb9b463c7e70324723d0

  ostree://rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
                   Version: 7.6.0 (2018-10-26 16:59:22)
                    Commit: 4330ddfb4b9f84c63edcea17928cd5cf1f8688e3e3297a63c18097defebf97a4
              GPGSignature: Valid signature by 567E347AD0044ADE55BA8A5F199E2F91FD431D51

# rpm -q podman
podman-0.10.1.3-4.gitee513cc.el7.x86_64

# podman run --rm -it docker.io/alpine ping -c 3 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes

--- 1.1.1.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss



Could we please get a new build made for RHEL 7.6 that includes the fix:

https://github.com/containers/libpod/commit/c611db2bc08df6bca8a921852998c842dae4f2cb
Comment 2 Micah Abbott 2018-11-15 14:38:32 UTC 
Matt, sorry to throw you under the bus, but Brent said you could spin a build for this?

I'd like to get this included in the next RHELAH release.
Comment 7 Joy Pu 2018-11-16 07:44:14 UTC 
Can not reproduce it in 7.6 env, so test it in 7.6 atomic image.
# podman run --rm -it docker.io/alpine ping -c 3 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes

--- 1.1.1.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

# rpm -Uvh /home/cloud-user/podman-0.11.1.1-3.git594495d.el7.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:podman-0.11.1.1-3.git594495d.el7 ################################# [ 50%]
Cleaning up / removing...
   2:podman-0.10.1.3-4.gitee513cc.el7 ################################# [100%]
# podman run --rm -it docker.io/alpine ping -c 3 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=44 time=38.268 ms
64 bytes from 1.1.1.1: seq=1 ttl=44 time=36.803 ms
64 bytes from 1.1.1.1: seq=2 ttl=44 time=36.756 ms

--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 36.756/37.275/38.268 ms

Set this to verified.
Comment 9 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
Note You need to log in before you can comment on or make changes to this bug.