Issue
The crc setup has WARN and ERRO failure issues causing UI, after login, to fail to load or load incompletely.
Error:
...
WARN Cluster is not ready: cluster operators are still not stable after ...
...
ERRO Cannot update kubeconfig: Head ... read: connection reset by peer
Below we have two possible workarounds:
- Workaround 1 - Cleanup
- Workaround 2 - Memory issue
Workaround 1 - Cleanup
1. Perform delete and clean-up:
$ crc stop
<wait>
$ crc delete -f
<wait>
$ crc cleanup
<wait for rules to be deleted, enter sudo password for modules, services, and etc hosts file to be cleaned up>
2. Perform new setup:
Note:
- If not OCP, override config by adding okd:
$ crc config set preset okd
<wait>
$ crc setup
<wait a bit, enter sudo password again for service and modules to be setup again>
$ crc start
<wait>
3. If successful, oc will have to be set-up again:
$ crc oc-env
<view output and enter>
e.g. export PATH="/home/myadminid/.crc/bin/oc:$PATH" ... eval $(crc oc-env)
$ export PATH="/home/myadminid/.crc/bin/oc:$PATH"
$ eval $(crc oc-env)
Workaround 2 - Limiting CRC Memory Usage
Note:
- With this workaround, the idea is that crc is using more memory than the OS allows, and the OS is shutting down crc services to gain back memory.
1. Verify your VM or workstation/server running has enough memory
$ free -h
<view Mem and Swap results - do you have at least 12 GB?>
2. After performing crc cleanup, and the new crc config, and crc setup, start crc start with a limit of memory to allocate:
$ crc start --memory 8192
previous page
|