Description of problem:
During UPI deployment on vmware we see that we weren't able to finish command:
/home/jenkins/bin/openshift-install wait-for install-complete --dir /home/jenkins/current-cluster-dir/openshift-cluster-dir --log-level INFO
Our jenkins job:
Actually we have 30 mins timeout to run this command and it got interrupted from our function run_cmd, so didn't finish in this timeout but I think that 30 mins is reasonable timeout as it's also used in IPI installer IIRC.
Should we wait more or this 30 mins is enough? If you can see some more details from logs please help us to understand what is wrong and stabilize our CI deployment over VmWare. Thanks
Must gather logs:
Version-Release number of selected component (if applicable):
4.3.1 GA version
Steps to Reproduce:
1. Install UPI on VmWare
2. Than wait for install complete with mentioned command
We didn't get cluster ready in 30 mins
Have installation done successfully.
Moving to Auth as the operator is still progressing.
And as for the timeout, the current expectation is that things should finish under 30 minutes.
Hi Petr, did this used to work with 4.2? I know some changes went into cri-o 1.16 (ocp 4.3) that lead to permission denied issues.
I do not remember this issue in 4.2 and actually I've seen this issue only once so far. If we will reproduce I will update here for sure but I've attached enough logs I hope from first occurrence.
Looked through the logs attached and not much info in there. Since this only happened once, and only happened on 1 out of the 3 nodes, it is very likely that this was a flake. Petr, please re-open if you run into this again.