Bug 2111467
| Summary: | Node internal DNS address is not set for machine | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Karthik K N <kabhat> |
| Component: | Cloud Compute | Assignee: | Karthik K N <kabhat> |
| Cloud Compute sub component: | Other Providers | QA Contact: | pdsilva |
| Status: | CLOSED ERRATA | Docs Contact: | Jeana Routh <jrouth> |
| Severity: | high | ||
| Priority: | unspecified | CC: | mimccune, mkumatag |
| Version: | 4.11 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.12.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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*])
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-01-17 19:53:34 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2111471 | ||
|
Description
Karthik K N
2022-07-27 11:08:25 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 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. thanks Karthik, i added your text to the bug form 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 |