2111474 – Fetch internal IPs of vms from dhcp server

Bug 2111474 - Fetch internal IPs of vms from dhcp server

Summary: Fetch internal IPs of vms from dhcp server

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Cloud Compute
Sub Component:
Version:	4.11
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Target Release:	4.12.0
Assignee:	Karthik K N
QA Contact:	pdsilva
Docs Contact:	Jeana Routh
URL:
Whiteboard:
Depends On:
Blocks:	2111475
TreeView+	depends on / blocked

Reported:	2022-07-27 11:21 UTC by Karthik K N
Modified:	2023-01-17 19:54 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	* Previously, Power VS cloud providers were not capable of fetching the machine IP address from DHCP server. Changing the IP address did not update the node, which caused some inconsistencies, such as pending certificate signing requests. With this release, the Power VS cloud provider is updated to fetch the machine IP address from the DHCP server so that the IP addresses for the nodes are consistent with the machine IP address. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2111474[BZ#2111474])
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 cloud-provider-powervs pull 10	0	None	Merged	Fetch internal IPs of vms from dhcp server	2022-07-27 11:21:17 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:21:18 UTC

Description of problem:
Currently Power VS cloud provider is not setting the Internal IP for node, Its the node just relaying on the kubelet set IP, This is causing some inconsistency and some csr are not being approved.

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

Comment 2 pdsilva 2022-09-07 14:31: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

Comment 4 Karthik K N 2022-11-24 12:12:14 UTC

Cause: Power VS cloud providers were not capable of fetching the machine IP address from DHCP server

Consequence: The node used to depend on the kubelet set IP during the booting of the machine and in case of any change in machine's IP address the node were never updated and which was causing some inconsistencies.

Fix: Updated Power VS cloud provider to fetch the machine's IP address from the DHCP server.

Result: The nodes IP address are consistent with the machine IP address and there is no inconsistency likes pending CSR.

Comment 5 Michael McCune 2022-11-28 15:40:35 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.