Bug 2049410

Summary:	external-dns-operator creates provider section, even when not requested
Product:	OpenShift Container Platform	Reporter:	Xander Soldaat <xsoldaat>
Component:	Networking	Assignee:	Andrey Lebedev <alebedev>
Networking sub component:	DNS	QA Contact:	Arvind iyengar <aiyengar>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	alebedev, aos-bugs, hongli, mmasters
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 10:46:22 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 Xander Soldaat 2022-02-02 07:25:06 UTC

Description of problem:
When using the external-dns-operator, the form view automatically injects an aws and infoblox section into the generated YAML file.

OpenShift release version:
external-dns-operator.v0.1.2 on 4.10FC2

Cluster Platform:
AWS

How reproducible:
Every time when creating an external DNS instance

Steps to Reproduce (in detail):
1.Install the external-dns-operator
2.Click create an instance
3.Click on YAML view, the aws and infoblox data should be there.


Actual results:
aws and infoblox section is there

Expected results:
no provider section unless I configured it

Impact of the problem:
Using the form is not possible, manual editing is required to remove the unwanted sections

Additional info:



** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report.  You may also mark the bug private if you wish.

Comment 1 Miciah Dashiel Butler Masters 2022-02-02 13:43:06 UTC

Setting blocker- as the issue can be worked around by manually editing the yaml.  However, this seems like an annoying UX that needs improvement.

Comment 4 Arvind iyengar 2022-03-31 12:22:56 UTC

Tested in release "4.11.0-0.nightly-2022-03-29-152521" version with the latest external DNS built from the main repo containing the fix. With this setup, the YAML view for external DNS creation looks cleaner without any additional entries in an AWS setup.

Comment 7 errata-xmlrpc 2022-08-10 10:46:22 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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069