Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionChristian Kellner
2020-09-10 16:00:55 UTC
In the osbuild-composer and koji-osbuild CI, we use a set of containers (a database one, a kerberos kdc one, one that is running koji hub and one for the builder). The use a custom network "org.osbuild.koji" and the containers want to talk to each other over network, addressing each other via their hostnames. This works fine on Fedora, but does not on RHEL, because the dnsname plugin is not shipped.
Thanks Jindrich for the information. Test with podman-plugins-2.1.1-3.module+el8.3.1+8686+2a59bca3.x86_64 and podman-2.1.1-3.module+el8.3.1+8686+2a59bca3.x86_64. It works as expect. Update the configure file and start two containers, try to ping one container from another. It works as expect. So set this to verified. Details:
# podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
40007cd2e480 localhost/testimg:latest top 4 seconds ago Up 4 seconds ago competent_clarke
]# podman run -it busybox
/ # ping competent_clarke
PING competent_clarke (10.88.0.6): 56 data bytes
64 bytes from 10.88.0.6: seq=0 ttl=64 time=0.061 ms
64 bytes from 10.88.0.6: seq=1 ttl=64 time=0.035 ms
64 bytes from 10.88.0.6: seq=2 ttl=64 time=0.051 ms
64 bytes from 10.88.0.6: seq=3 ttl=64 time=0.051 ms
^C
--- competent_clarke ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.035/0.049/0.061 ms
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 (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), 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/RHSA-2021:0531