Description of problem:
An infra object in some vsphere deployments can look like this:
~]$ oc get infrastructure cluster -o json | jq .status { "apiServerInternalURI": "xxx", "apiServerURL": "xxx", "controlPlaneTopology": "HighlyAvailable", "etcdDiscoveryDomain": "", "infrastructureName": "xxx", "infrastructureTopology": "HighlyAvailable", "platform": "VSphere", "platformStatus": { "type": "VSphere" } }
Which if we attempt to run the regenerate MCO command in https://access.redhat.com/articles/regenerating_cluster_certificates will cause a panic
Version-Release number of selected component (if applicable):
4.10.65 4.11.47 4.12.29 4.13.8 4.14.0 4.15
How reproducible:
100%
Steps to Reproduce:
1. Run procedure on cluster with above infra 2. 3.
Actual results:
panic
Expected results:
no panic
Additional info:
- blocks
-
OCPBUGS-20508 Regenerating the machine config operator certificates can panic on vSphere
- Closed
- is cloned by
-
OCPBUGS-20508 Regenerating the machine config operator certificates can panic on vSphere
- Closed
-
OCPBUGS-21871 Should optimize the output for command `oc adm ocp-certificates regenerate-machine-config-server-serving-cert`
- Closed
- links to
-
RHEA-2023:7198 rpm