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 2073958 - Podman v3.4.2 regression with hosts file breaks getHostAddress() call
Summary: Podman v3.4.2 regression with hosts file breaks getHostAddress() call
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Alex Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-11 08:47 UTC by Suhaas Bhat
Modified: 2022-11-08 09:32 UTC (History)
11 users (show)

Fixed In Version: podman-4.1.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:15:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-118514 0 None None None 2022-04-11 09:01:56 UTC
Red Hat Product Errata RHSA-2022:7457 0 None None None 2022-11-08 09:16:34 UTC

Description Suhaas Bhat 2022-04-11 08:47:26 UTC
Description of problem:
Updating to podman version 3.4 fails to fetch the local host name.

Version-Release number of selected component (if applicable):
podman-3.4.2-9.module+el8.5.0+13852+150547f7.x86_64

How reproducible:
Fully 

Steps to Reproduce:
https://github.com/containers/podman/issues/12003#issuecomment-991968895

Actual results:
Does not update hostnames

Expected results:
Should be able to update hostnames.

Additional info:

Comment 5 Daniel Walsh 2022-04-12 18:03:43 UTC
I would prefer to have customers wait for podman 4.1 if at all possible.

Comment 19 Alex Jia 2022-05-16 13:26:20 UTC
This bug has been verified on podman-4.1.0-2.module+el8.7.0+15223+3987d347.

[root@hpe-dl380pgen8-02-vm-1 ~]# podman run --name c4 --pod test fedora cat /etc/hosts
127.0.0.1	localhost localhost.localdomain localhost4 localhost4.localdomain4
::1	localhost localhost.localdomain localhost6 localhost6.localdomain6
10.88.0.1	host.containers.internal
10.88.0.11	test 64bac61c4b61-infra
127.0.0.1	c3
127.0.0.1	c4

Comment 21 errata-xmlrpc 2022-11-08 09:15:45 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 (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-2022:7457


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