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.
Description of problem:
Resolv::DNS does not return any results under those conditions:
there are at least two name servers (in /etc/resolv.conf).
The name servers have IPv6 addresses containing leading zeros.
Example resolv.conf:
nameserver 2001:0db8::0001:1
nameserver 2001:0db8::0002:1
This is caused by a mismatch in representation of the address: Requester::sender_for compares the address of the answering server (e.g. 2001:0db8::1:1) with the address the request was sent to (e.g. 2001:0db8::0001:1).
Version-Release number of selected component (if applicable):
ruby-libs-2.5.5-105.module+el8.1.0+3656+f80bfa1d.x86_64
How reproducible:
We reproduced this by running puppet_facts on OSP 16.1
Steps to Reproduce:
You can see the difference in timing when the ipa facts are pre-populated (the DNS lookup is skipped) or not:
[root@]# time FACTER_ipa_domain='' FACTER_ipa_server='' puppet facts >/dev/null
real 0m2.367s
user 0m1.746s
sys 0m0.392s
[root@]# time puppet facts >/dev/null
real 1m22.435s
user 0m1.735s
sys 0m0.428s
Additional info:
See https://bugzilla.redhat.com/show_bug.cgi?id=1916404
This was fixed in https://bugs.ruby-lang.org/issues/16439
Description of problem: Resolv::DNS does not return any results under those conditions: there are at least two name servers (in /etc/resolv.conf). The name servers have IPv6 addresses containing leading zeros. Example resolv.conf: nameserver 2001:0db8::0001:1 nameserver 2001:0db8::0002:1 This is caused by a mismatch in representation of the address: Requester::sender_for compares the address of the answering server (e.g. 2001:0db8::1:1) with the address the request was sent to (e.g. 2001:0db8::0001:1). Version-Release number of selected component (if applicable): ruby-libs-2.5.5-105.module+el8.1.0+3656+f80bfa1d.x86_64 How reproducible: We reproduced this by running puppet_facts on OSP 16.1 Steps to Reproduce: You can see the difference in timing when the ipa facts are pre-populated (the DNS lookup is skipped) or not: [root@]# time FACTER_ipa_domain='' FACTER_ipa_server='' puppet facts >/dev/null real 0m2.367s user 0m1.746s sys 0m0.392s [root@]# time puppet facts >/dev/null real 1m22.435s user 0m1.735s sys 0m0.428s Additional info: See https://bugzilla.redhat.com/show_bug.cgi?id=1916404 This was fixed in https://bugs.ruby-lang.org/issues/16439