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.
Comment 6Pavel Šimerda (pavlix)
2013-01-22 11:15:09 UTC
(In reply to comment #5)
> Pavel, do you agree that this is caused by AI_ADDRCONFIG? Are there any
> plans to fix getaddrinfo() in RHEL-6?
>
> https://fedoraproject.org/wiki/Networking/NameResolution/ADDRCONFIG
Looks like. Resolution of 127.0.0.1 with AI_ADDRCONFIG on a host with only 127.0.0.1 fails. Using 'localhost' instead should work as a workaround to connect through IPv6.
I'm working on upstream patches and even that is a long run. Can't speak for RHEL. Forwarding the question to Carlos.
I can't comment on the availability of a fix for this in RHEL 6.
I am aware of these issues and they are at the top of my priority list to fix.
Unfortunately they are complex and create significant compatibility risk which requires thorough testing to ensure we don't break userspace.
Thank you for your patience :-)
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
This issue does not qualify, but we will consider incorporating an upstream change into Red Hat Enterprise Linux 7 if it becomes available.
Comment 24Red Hat Bugzilla Rules Engine
2017-11-08 09:26:12 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Most applications have workarounds in place for AI_ADDRCONFIG and localhost access. Changing this behaviour in any released version of RHEL will have serious repercussions for the workarounds. We also believe that this may be unfixable upstream except perhaps in a future glibc 3.0, for all the same reasons we can't easily fix this in RHEL. I'm going to mark this as CLOSED/WONTFIX, and we'll track this issue upstream in: https://sourceware.org/bugzilla/show_bug.cgi?id=12398.