Bug 1971863

Summary:	Queries of type 'ANY' are deprecated - RFC8482
Product:	[oVirt] ovirt-setup-lib	Reporter:	Strahil Nikolov <hunter86_bg>
Component:	General	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.3.2	CC:	bugs, gdeolive, mavital, sbonazzo
Target Milestone:	ovirt-4.5.0	Flags:	sbonazzo: ovirt-4.5+ sbonazzo: devel_ack+ gdeolive: testing_ack+
Target Release:	1.3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-setup-lib-1.3.3	Doc Type:	Bug Fix
Doc Text:	Cause: Queries of type 'ANY' are deprecated - RFC8482 Consequence: Warning is issued when DNS does not respond at all: Failed to resolve FQDN using DNS, it can be resolved only locally Fix: package has been patched for do not use DNS query type ANY Result: no warning issues and FQDN is correctly resolved.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-28 09:26:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2044362

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.