It seems Scenario 1 always works OK, but Scenario 2 fails. Scenario 1 uses vmWare, and Secnario 2 uses VirtualBox. In both scenarios I have completely cleared down the environments, downloaded the latest CRC. I am running Centos 7 on a System with 32 GB memory & having Intel® Core™ i5-4440S CPU 2.80GHz × 4 mail is handled by 10 .Įrror: fatal: unable to access '': Could not resolve host: ītw. Check below output on command line of 192.168.130.11 Ssh -i ~/.crc/machines/crc/id_ecdsa able to successfully resolve from the shell. In fact, I am able login to host using command When executed separately (without timeout) "oc get nodes" command works fine and output isĬrc-pkjt4-master-0 Ready master,worker 18d v1.20.0+df9c838Ģ] Well even then crc is up and I am able to login but build never succeeds. Level=debug msg="error: Temporary error: ssh command error:\ncommand : timeout 5s oc get nodes -context admin -cluster crc -kubeconfig /opt/kubeconfig\nerr : Process exited with status 1\n - sleeping 1s"Īny mechanism to increase timeout in "timeout 5s oc get nodes -context admin -cluster crc -kubeconfig /opt/kubeconfig"? Level=debug msg="The connection to the server :6443 was refused - did you specify the right host or port?\n" Level=debug msg="SSH command results: err: Process exited with status 1, output: " Level=debug msg="Running SSH command: timeout 5s oc get nodes -context admin -cluster crc -kubeconfig /opt/kubeconfig" When run in debug mode I get following mesages "Waiting for kube-apiserver availability. 1] Never able to successfully execute crc start.
0 kommentar(er)
