Back to bug 1902307

Who When What Removed Added
Joel Speed 2020-11-30 10:36:02 UTC Target Release --- 4.7.0
Assignee agarcial jspeed
Severity unspecified medium
Michael McCune 2020-12-04 16:39:15 UTC Keywords UpcomingSprint
CC mimccune
Eric Paris 2020-12-09 13:30:23 UTC Keywords UpcomingSprint
Joel Speed 2021-01-05 17:24:43 UTC Target Release 4.7.0 ---
Joel Speed 2021-02-08 10:16:56 UTC Assignee jspeed aos-cloud-bugs
Joel Speed 2021-03-25 15:37:10 UTC Status NEW ASSIGNED
Assignee aos-cloud-bugs dmoiseev
Joel Speed 2021-08-19 10:21:14 UTC CC dmoiseev
Flags needinfo?(dmoiseev)
Joel Speed 2021-10-12 11:47:51 UTC Flags needinfo?(dmoiseev)
CC rkant
Sub Component Other Providers Cloud Controller Manager
CC aos-bugs, aos-cloud-bugs
Mike Fedosin 2021-10-14 10:52:47 UTC CC mfedosin
Joel Speed 2022-01-14 12:46:12 UTC Priority unspecified medium
Joel Speed 2022-03-09 12:52:00 UTC Target Release --- 4.11.0
Status ASSIGNED POST
Jeff Fearn 🐞 2022-04-11 08:33:48 UTC CC aos-cloud-bugs
Joel Speed 2022-05-24 09:57:40 UTC Link ID Github openshift/kubernetes/pull/1252
Joel Speed 2022-05-26 13:55:30 UTC Status POST ASSIGNED
OpenShift BugZilla Robot 2022-06-01 14:50:50 UTC Status ASSIGNED POST
OpenShift BugZilla Robot 2022-06-01 14:50:52 UTC Link ID Github openshift/cluster-kube-controller-manager-operator/pull/631
OpenShift BugZilla Robot 2022-06-20 14:33:42 UTC Status POST MODIFIED
OpenShift Automated Release Tooling 2022-06-20 14:38:47 UTC Status MODIFIED ON_QA
sunzhaohua 2022-06-21 01:44:43 UTC QA Contact zhsun huliu
Huali Liu 2022-06-22 05:53:50 UTC Status ON_QA VERIFIED
errata-xmlrpc 2022-08-10 10:35:34 UTC Doc Type If docs needed, set a value Bug Fix
Doc Text Cause:
Getting nodes zone labels requires to contact vCenter for obtain that labels values. Due to kubelet tries to do so in a very early initialisation steps it can not read vCenter credentials from the secrets.

Consequence:
In case if
Doc Text vCenter credentials stored in secret and regions/zone parameters are presented in cloud.conf, kubelet can not start
Doc Text , due to lack of credentials for vCenter for obtaining zone/region label values.

Fix:
For vSphere platform with set up secret region and zone labels population was moved out of kubelet initialization sequence to the kube-controller-manager part
Doc Text of cloud provider code.

Result:
Region and zone labels works properly and do not cause kubelet hanging with credentials in secret now.
Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2022-08-10 10:35:34 UTC
errata-xmlrpc 2022-08-10 10:36:06 UTC Link ID Red Hat Product Errata RHSA-2022:5069

Back to bug 1902307