Bug 1920905 - Remove DNS lookup workaround from cluster-api-provider
Summary: Remove DNS lookup workaround from cluster-api-provider
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Evgeny Slutsky
QA Contact: Michael Burman
Depends On:
Blocks: 1939358
TreeView+ depends on / blocked
Reported: 2021-01-27 08:53 UTC by Evgeny Slutsky
Modified: 2021-07-27 22:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:36:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-api-provider-ovirt pull 85 0 None open WIP: extract node machine ipaddress from the engine instead using DNS . 2021-02-18 08:58:39 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:37:15 UTC

Description Evgeny Slutsky 2021-01-27 08:53:20 UTC
Description of problem:

in ocp-on-rhv deployments, machine DNS resolutions are handled by ocp external DNS services.

using DNS lookup for node IP  retrieval proved to be unpredictable in some cases,

since 4.7 qemu-agent was introduced into RCHOS installation [0],
so oVirt engine uses qemu-agent to query and save each VM IP Address.
we want to replace the DNS lookup mechanism by querying this info using oVirt SDK.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1900759

Comment 5 Michael Burman 2021-03-22 13:06:14 UTC
Verified on - 4.8.0-0.nightly-2021-03-19-075500

Comment 10 errata-xmlrpc 2021-07-27 22:36:45 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: OpenShift Container Platform 4.8.2 bug fix and security 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.


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