Bug 1971863 - Queries of type 'ANY' are deprecated - RFC8482
Summary: Queries of type 'ANY' are deprecated - RFC8482
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-setup-lib
Classification: oVirt
Component: General
Version: 1.3.2
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ovirt-4.5.0
: 1.3.3
Assignee: Yedidyah Bar David
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks: 2044362
TreeView+ depends on / blocked
 
Reported: 2021-06-14 20:58 UTC by Strahil Nikolov
Modified: 2022-04-28 09:26 UTC (History)
4 users (show)

Fixed In Version: ovirt-setup-lib-1.3.3
Clone Of:
Environment:
Last Closed: 2022-04-28 09:26:34 UTC
oVirt Team: Integration
Embargoed:
sbonazzo: ovirt-4.5+
sbonazzo: devel_ack+
gdeolive: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 116975 0 master MERGED hostname: Do not use DNS query type ANY 2021-10-06 13:04:24 UTC

Description Strahil Nikolov 2021-06-14 20:58:14 UTC 
Description of problem:
At https://github.com/oVirt/ovirt-setup-lib/blob/master/src/ovirt_setup_lib/hostname.py#L398-L404 we are using query of type 'ANY' but it is deprecated. Servers might return any kind of data (or no data at all).

Version-Release number of selected component (if applicable):
N/A

How reproducible:
always

Steps to Reproduce:
1.Run 'engine-setup'

Actual results:
Warning is issued when DNS does not respond at all:
Failed to resolve FQDN using DNS, it can be 
resolved only locally

Expected results:
isResolvedByDNS should issue 2 queries -> for A and AAAA records

Additional info:
https://blog.cloudflare.com/rfc8482-saying-goodbye-to-any/
Comment 1 RHEL Program Management 2021-06-15 06:11:56 UTC 
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Comment 2 Yedidyah Bar David 2021-10-06 05:24:41 UTC 
Sandro - see bug 2010658. Perhaps we want a tracker to cover all places - not sure exactly how to find them. Perhaps change current to 4.4.9 as well.
Comment 3 Yedidyah Bar David 2021-10-06 13:07:34 UTC 
Patch merged to master. I think it's safe to backport to 4.4 and move the bug to 4.4.9, even though it's not that critical (just prevent a warning). Keeping in POST waiting for a decision...
Comment 4 Yedidyah Bar David 2021-10-07 06:55:00 UTC 
Will keep in 4.5 for now.
Comment 5 Strahil Nikolov 2021-12-31 15:58:31 UTC 
The patch from https://gerrit.ovirt.org/116975 works even on oVirt 4.3.10
Comment 6 Yedidyah Bar David 2022-01-02 07:14:44 UTC 
(In reply to Strahil Nikolov from comment #5)
> The patch from https://gerrit.ovirt.org/116975 works even on oVirt 4.3.10

Thanks for checking! oVirt 4.3 is EOL, and I am not aware of plans to back-port this patch.
Comment 8 Sandro Bonazzola 2022-04-28 09:26:34 UTC 
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.