crc: [BUG] crc start fails on ` Waiting until the user's pull secret is written to the instance disk...` step
General information
- OS: Linux
- Hypervisor: KVM
- Did you run
crc setupbefore starting it (Yes/No)? yes - Running CRC on: Laptop
CRC version
CRC version: 2.34.1+b470b5
OpenShift version: 4.15.3
Podman version: 4.4.4
CRC status
crc status --log-level debug
DEBU CRC version: 2.34.1+b470b5
DEBU OpenShift version: 4.15.3
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
CRC VM: Running
OpenShift: Unreachable (v4.15.3)
RAM Usage: 1.932GB of 10.96GB
Disk Usage: 19.05GB of 32.68GB (Inside the CRC VM)
Cache Usage: 26.27GB
Cache Directory: /home/tlavocat/.crc/cache
CRC config
crc config view
- consent-telemetry : yes
Host Operating System
NAME="Fedora Linux"
VERSION="39 (Workstation Edition)"
ID=fedora
VERSION_ID=39
VERSION_CODENAME=""
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Linux 39 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:39"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f39/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=39
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=39
SUPPORT_END=2024-11-12
VARIANT="Workstation Edition"
VARIANT_ID=workstation
Steps to reproduce
- crc setup
- crc start -p ~/Documents/pull-secret
Expected
I expect a normal startup.
Actual
Error waiting for apiserver: Temporary error: ssh command error:
command : timeout 5s oc get nodes --context admin --cluster crc --kubeconfig /opt/kubeconfig
err : Process exited with status 1
(x222)
Logs
Before gather the logs try following if that fix your issue
$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug
Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.
See: https://gist.github.com/lavocatt/3f5d8fca0ac3ad52ddae982b906c3080
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 19 (3 by maintainers)
Commits related to this issue
- [hack] bump crc to 2.34.1 / openshift 4.15 see https://github.com/crc-org/crc/issues/4110#issuecomment-2085562237 — committed to jmazzitelli/kiali by jmazzitelli 3 years ago
- [hack] bump crc to 2.34.1 / openshift 4.15 (#7316) * [hack] bump crc to 2.34.1 / openshift 4.15 see https://github.com/crc-org/crc/issues/4110#issuecomment-2085562237 * add cleanup. now delete ... — committed to kiali/kiali by jmazzitelli 3 years ago
After investigating with Fedora-CSB laptops looks like the
systemd-resolvedservice is running but not consumed byNetworkManagerso crc’s preflight checks add the dispatcher file which is doesn’t work since/etc/resolv.confis not managed bysystemd-resolvedand in this case in the VM internal dns resolutions fails. We have 2 different workaroundWorkaround-1: Disable/mask the
systemd-resolvedand follow the stepsWorkaround-2: Make sure
/etc/resolv.confmanaged bysystemd-resolved@praveenkumar just so I’m clear - the workarounds you mentioned, are those going to be the final solution for those with this problem? Or is the plan for CRC to change in a future version so the workarounds will not be needed?
Would stil be nice to fix the DNS resolution problem you were having 😃