Bug 2061549

Summary:	AzureStack install with internal publishing does not create api DNS record
Product:	OpenShift Container Platform	Reporter:	Matthew Staebler <mstaeble>
Component:	Installer	Assignee:	Nobody <nobody>
Installer sub component:	openshift-installer	QA Contact:	Mike Gahagan <mgahagan>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	high	CC:	anarayan
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The DNS record for the api was only being created when the cluster type was public Consequence: Internal clusters did not have an api record even though it is needed but needs the ip of the internal cluster Fix: Removed the check for creating the api cluster if the cluster is public Result: api records are created for internal clusters	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 10:52:44 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 Matthew Staebler 2022-03-07 19:38:08 UTC

When doing an install to Azure Stack Hub with internal publishing, the DNS record for the api is not created. The intention is to create the api DNS record with the IP address of the internal load balancer.

Comment 3 Mike Gahagan 2022-03-22 19:36:25 UTC

I'm able to see the api dns record being created now, but installation is failing due to other issues that I'm currently investigating

Comment 4 Mike Gahagan 2022-03-29 17:43:42 UTC

ok I can confirm the installation is going far enough along that the dns records are getting created and we can verify this bug.

Comment 8 errata-xmlrpc 2022-08-10 10:52:44 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