Bug 2111467 - Node internal DNS address is not set for machine
Summary: Node internal DNS address is not set for machine
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.12.0
Assignee: Karthik K N
QA Contact: pdsilva
Jeana Routh
URL:
Whiteboard:
Depends On:
Blocks: 2111471
TreeView+ depends on / blocked
 
Reported: 2022-07-27 11:08 UTC by Karthik K N
Modified: 2023-01-17 19:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* Previously, when the Machine API provider failed to fetch the machine IP address, it would not set the internal DNS name and the machine certificate signing requests were not automatically approved. With this release, the Power VS machine provider is updated to set the server name as the internal DNS name even when it fails to fetch the IP address. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2111467[*BZ#2111467*])
Clone Of:
Environment:
Last Closed: 2023-01-17 19:53:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-api-provider-powervs pull 27 0 None Merged Set the node internal dns address for machine 2022-07-27 11:08:25 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:54:01 UTC

Description Karthik K N 2022-07-27 11:08:25 UTC 
Description of problem:

For a Power VS machine when it fails to fetch the internal IP from DHCP server, Its skipping to set the Node Internal DNS address for machine, This leads to csr being not approved and machine never becomes node.

Version-Release number of selected component (if applicable):

4.11
Comment 2 pdsilva 2022-09-07 14:33:55 UTC 
Verified with 4.12.0-0.nightly-ppc64le-2022-09-07-045824
No csr was pending post deployment

# oc get clusterversion
ocNAME      VERSION                                      AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.0-0.nightly-ppc64le-2022-09-07-045824   True        False         2m5s    Cluster version is 4.12.0-0.nightly-ppc64le-2022-09-07-045824

# oc get nodes -owide
NAME                                       STATUS   ROLES                  AGE    VERSION           INTERNAL-IP    EXTERNAL-IP    OS-IMAGE                                                        KERNEL-VERSION                  CONTAINER-RUNTIME
rdr-ipi-sao1-412-3-pr-mqxqz-master-0       Ready    control-plane,master   133m   v1.24.0+ebabf6d   192.168.0.11   192.168.0.11   Red Hat Enterprise Linux CoreOS 412.86.202209062338-0 (Ootpa)   4.18.0-372.19.1.el8_6.ppc64le   cri-o://1.25.0-51.rhaos4.12.git315a0cb.el8
rdr-ipi-sao1-412-3-pr-mqxqz-master-1       Ready    control-plane,master   133m   v1.24.0+ebabf6d   192.168.0.12   192.168.0.12   Red Hat Enterprise Linux CoreOS 412.86.202209062338-0 (Ootpa)   4.18.0-372.19.1.el8_6.ppc64le   cri-o://1.25.0-51.rhaos4.12.git315a0cb.el8
rdr-ipi-sao1-412-3-pr-mqxqz-master-2       Ready    control-plane,master   133m   v1.24.0+ebabf6d   192.168.0.10   192.168.0.10   Red Hat Enterprise Linux CoreOS 412.86.202209062338-0 (Ootpa)   4.18.0-372.19.1.el8_6.ppc64le   cri-o://1.25.0-51.rhaos4.12.git315a0cb.el8
rdr-ipi-sao1-412-3-pr-mqxqz-worker-87pk4   Ready    worker                 110m   v1.24.0+ebabf6d   192.168.0.14   192.168.0.14   Red Hat Enterprise Linux CoreOS 412.86.202209062338-0 (Ootpa)   4.18.0-372.19.1.el8_6.ppc64le   cri-o://1.25.0-51.rhaos4.12.git315a0cb.el8
rdr-ipi-sao1-412-3-pr-mqxqz-worker-k97w7   Ready    worker                 110m   v1.24.0+ebabf6d   192.168.0.15   192.168.0.15   Red Hat Enterprise Linux CoreOS 412.86.202209062338-0 (Ootpa)   4.18.0-372.19.1.el8_6.ppc64le   cri-o://1.25.0-51.rhaos4.12.git315a0cb.el8
rdr-ipi-sao1-412-3-pr-mqxqz-worker-w8n2s   Ready    worker                 110m   v1.24.0+ebabf6d   192.168.0.16   192.168.0.16   Red Hat Enterprise Linux CoreOS 412.86.202209062338-0 (Ootpa)   4.18.0-372.19.1.el8_6.ppc64le   cri-o://1.25.0-51.rhaos4.12.git315a0cb.el8
Comment 4 Karthik K N 2022-11-24 12:01:31 UTC 
Cause: Machine api providers were failing to fetch the machine's ip address and skipping to set the Internal DNS name.

Consequence: The machine csrs were not automatically approved.

Fix: Updated Power VS machine provider to set the Server name as Internal DNS name irrespective of failing to fetch machine ip address.

Result: With the newly created clusters the machines csrs are automatically approved and no pending csrs were seen.
Comment 5 Michael McCune 2022-11-28 15:39:32 UTC 
thanks Karthik, i added your text to the bug form
Comment 7 errata-xmlrpc 2023-01-17 19:53:34 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.12.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:7399
Note You need to log in before you can comment on or make changes to this bug.