-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
4.13.0
-
No
-
False
-
Description of problem:
I discussed this here: https://redhat-internal.slack.com/archives/CNSJG0ZED/p1677843904013489 Where installer is failing with: couldn't get current server API group list: Get "https://api-int.odf-cl.qe.rh-ocs.com:6443/api?timeout=32s": dial tcp 10.1.112.11:6443: i/o timeout
Version-Release number of selected component (if applicable):
latest nightly 4.13 build
How reproducible:
Deploy OCP 4.13 nightly on top of RHV via IPI - RHV is with single hypervisor using SD on the hypervisor.
Steps to Reproduce:
1. Install OCP 4.13 on top of RHV 2. 3.
Actual results:
Installation is failing because API is not available because no node VM get's static IP provided for
Expected results:
IPI installation pass
Additional info:
Installer log: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-017ri1c33-t1/j-017ri1[…]0303T091146/openshift-cluster-dir/.openshift_install.log Gather bootstrap: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-017ri1c33-t1/j-017ri1c33-t1_20230303T091146/openshift-cluster-dir/log-bundle-20230303120436.tar.gz The deployment type is IPI over RHV env with single node using local storage on the node. The same deployment works just fine with latest 4.12 version and stopped working with 4.13. Noticed that in RHV env we don't see any of static IP for Ingress and API is assigned to any of VM, see screenshots in slack thread. In 4.12 deployment I see those IPs are on two nodes from RHV UI.