Bug 2061549 - AzureStack install with internal publishing does not create api DNS record
Summary: AzureStack install with internal publishing does not create api DNS record
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.11.0
Assignee: Nobody
QA Contact: Mike Gahagan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-07 19:38 UTC by Matthew Staebler
Modified: 2022-08-10 10:53 UTC (History)
1 user (show)

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
Clone Of:
Environment:
Last Closed: 2022-08-10 10:52:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5691 0 None open Bug 2061549: azurestack: create the api DNS record when publishing internally 2022-03-08 18:25:18 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:53:04 UTC

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
Note You need to log in before you can comment on or make changes to this bug.