Bug 1912571

Summary:	libvirt: Support setting dnsmasq options through the install config
Product:	OpenShift Container Platform	Reporter:	Prashanth Sundararaman <psundara>
Component:	Multi-Arch	Assignee:	Deep Mistry <dmistry>
Status:	CLOSED ERRATA	QA Contact:	Barry Donahue <bdonahue>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.7	CC:	amccrae, bleanhar, danili
Target Milestone:	---
Target Release:	4.8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 22:35:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Prashanth Sundararaman 2021-01-04 19:35:30 UTC

Libvirt does not support dns wildcard resolution, so typically for the *.apps entries to be routed to the workers, we do this workaround:

https://github.com/openshift/installer/blob/master/docs/dev/libvirt/README.md#console-doesnt-come-up

But this becomes a little hard to implement when we have automation as is the case with multi-arch CI which runs on libvirt. Today we do this hack:

https://github.com/openshift/release/blob/master/ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml#L532-L554

where we wait for the network to come up and modify the host records. In addition to this, with the current workaround upgrades are problematic as the route would only point to one worker.

In libvirt 5.6+, there is an option to specify dnsmasq options through the network xml itself and the terraform provider has support for adding this option:

https://github.com/dmacvicar/terraform-provider-libvirt/pull/820

It would be ideal to be able to specify the dnsmasq options through the install config so it can be plumbed all the way through terraform to the xml.

This would make the CI cleaner and also give us the ability to change it dynamically for each cluster rather than messing with the libvirt network.

Comment 4 Dan Li 2021-02-01 15:22:07 UTC

Hi Prashanth, do you think this bug will be resolved before the end of the current sprint (Feb. 6th)? If not, can we set the "Reviewed-in-Sprint" flag to "+"?

Comment 6 Prashanth Sundararaman 2021-02-12 16:50:57 UTC

verified by installing a cluster on libvirt using the dnsmasq option.

Comment 7 Dan Li 2021-03-18 13:24:33 UTC

Re-assigning this under Deep's name since he has it integrated in the CI; however, since this bug is VERIFIED, we are just waiting for the bug to be closed.

Comment 10 errata-xmlrpc 2021-07-27 22:35:38 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.

https://access.redhat.com/errata/RHSA-2021:2438