crc: [BUG] "Unable to determine VM's IP address, did it fail to boot?" on a RHEL 8.6 VM
General information
- OS: Linux
- Hypervisor: KVM
- Did you run
crc setupbefore starting it (Yes/No)? Yes - Running CRC on: VM
CRC version
CRC version: 2.10.1+426703d
OpenShift version: 4.11.7
Podman version: 4.2.0
CRC status
DEBU CRC version: 2.10.1+426703d
DEBU OpenShift version: 4.11.7
DEBU Podman version: 4.2.0
DEBU Running 'crc status'
DEBU Checking file: /home/fmean/.crc/machines/crc/.crc-exist
DEBU Checking file: /home/fmean/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/fmean/.crc/bin/crc-driver-libvirt
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address 127.0.0.1:36273
DEBU () Calling .GetVersion
DEBU Using API Version 1
DEBU () Calling .SetConfigRaw
DEBU () Calling .GetMachineName
DEBU (crc) Calling .GetBundleName
DEBU (crc) Calling .GetState
DEBU (crc) DBG | time="2022-10-26T06:20:48Z" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2022-10-26T06:20:48Z" level=debug msg="Fetching VM..."
DEBU (crc) Calling .GetIP
DEBU (crc) DBG | time="2022-10-26T06:20:48Z" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2022-10-26T06:20:48Z" level=debug msg="Getting current state..."
DEBU (crc) Calling .GetIP
DEBU (crc) DBG | time="2022-10-26T06:20:48Z" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2022-10-26T06:20:48Z" level=debug msg="Getting current state..."
DEBU Running SSH command: df -B1 --output=size,used,target /sysroot | tail -1
DEBU Using ssh private keys: [/home/fmean/.crc/machines/crc/id_ecdsa /home/fmean/.crc/cache/crc_libvirt_4.11.7_amd64/id_ecdsa_crc]
DEBU SSH command results: err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain, output:
DEBU Cannot get root partition usage: ssh command error:
command : df -B1 --output=size,used,target /sysroot | tail -1
err : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBU cannot get OpenShift status: stat /home/fmean/.crc/machines/crc/kubeconfig: no such file or directory
DEBU Making call to close driver server
DEBU (crc) Calling .Close
DEBU Successfully made call to close driver server
DEBU Making call to close connection to plugin binary
DEBU (crc) DBG | time="2022-10-26T06:20:48Z" level=debug msg="Closing plugin on server side"
CRC VM: Running
OpenShift: Unreachable (v4.11.7)
Podman:
Disk Usage: 0B of 0B (Inside the CRC VM)
Cache Usage: 13.05GB
Cache Directory: /home/fmean/.crc/cache
CRC config
- consent-telemetry : no
Host Operating System
NAME="Red Hat Enterprise Linux"
VERSION="8.6 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.6"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.6 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.6"
Steps to reproduce
- crc setup
- crc start --log-level debug
Expected
VM created and ready to be used
Actual
The CRC VM is not created at all. It does try 60 times then it exits but the error is not really helpful. I currently have no clue what could be the issue. I am trying to install this on a RHEL 8.6 VM created via VMWare. I see a “handshake failed” error when executing CRC status but I do not know if it is relevant since the VM is not created.
Logs
Before gather the logs try following if that fix your issue
$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug
I did those steps after the first failed attempt and it gives the same results.
Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.
https://gist.github.com/Kerthal/888dc38334bd3341b681c255159c31b6#file-crc-log-txt
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (7 by maintainers)
Unfortunately, as Gerard mentioned before:
We don’t test crc nested on VMWare, so I have no idea where this issue with networking is coming from. Maybe try user mode networking and see if that’s better (
crc config set network-mode user)