Bug 1950331 - rh-ruby26-ruby: Resolv::DNS: timeouts if multiple IPv6 name servers are given and address contains leading zero [rhscl-3]
Summary: rh-ruby26-ruby: Resolv::DNS: timeouts if multiple IPv6 name servers are given...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: ruby
Version: rh-ruby26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 3.7
Assignee: Vít Ondruch
QA Contact: Dita Stehlikova
URL:
Whiteboard:
Depends On:
Blocks: 1916404
TreeView+ depends on / blocked
 
Reported: 2021-04-16 12:40 UTC by Vít Ondruch
Modified: 2021-07-22 16:05 UTC (History)
3 users (show)

Fixed In Version: rh-ruby26-ruby-2.6.7-119.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-03 11:26:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2021-04-16 12:40:14 UTC
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

Comment 8 errata-xmlrpc 2021-06-03 11:26:06 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: rh-ruby26-ruby 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:2230


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