Tuesday, 15 June 2021

CRC setup error

 If you have an error running CRC setup, restart and add more memory and CPU and rerun the following:

$ crc delete
$ crc cleanup
$ crc setup
$ crc start

https://github.com/code-ready/crc/issues/1485


[mars@rhel83 ~]$ crc setup

INFO Checking if running as non-root

INFO Checking if running inside WSL2

INFO Checking if admin-helper executable is cached

INFO Checking if running on a supported CPU architecture

INFO Checking minimum RAM requirements

INFO Checking if Virtualization is enabled

INFO Checking if KVM is enabled

INFO Checking if libvirt is installed

INFO Checking if user is part of libvirt group

INFO Checking if active user/process is currently part of the libvirt group

INFO Checking if libvirt daemon is running

INFO Checking if a supported libvirt version is installed

INFO Checking if crc-driver-libvirt is installed

INFO Checking if systemd-networkd is running

INFO Checking if NetworkManager is installed

INFO Checking if NetworkManager service is running

INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists

INFO Writing Network Manager config for crc

INFO Using root access: Writing NetworkManager configuration to /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf

[sudo] password for mars:

INFO Using root access: Changing permissions for /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf to 644

INFO Using root access: Executing systemctl daemon-reload command

INFO Using root access: Executing systemctl reload NetworkManager

INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists

INFO Writing dnsmasq config for crc

INFO Using root access: Writing NetworkManager configuration to /etc/NetworkManager/dnsmasq.d/crc.conf

INFO Using root access: Changing permissions for /etc/NetworkManager/dnsmasq.d/crc.conf to 644

INFO Using root access: Executing systemctl daemon-reload command

INFO Using root access: Executing systemctl reload NetworkManager

INFO Checking if libvirt 'crc' network is available

INFO Setting up libvirt 'crc' network

INFO Checking if libvirt 'crc' network is active

INFO Starting libvirt 'crc' network

INFO Checking if CRC bundle is extracted in '$HOME/.crc'

INFO Checking if /home/mars/.crc/cache/crc_libvirt_4.7.11.crcbundle exists

Your system is correctly setup for using CodeReady Containers, you can now run 'crc start' to start the OpenShift cluster

[mars@rhel83 ~]$ crc start

INFO Checking if running as non-root

INFO Checking if running inside WSL2

INFO Checking if admin-helper executable is cached

INFO Checking if running on a supported CPU architecture

INFO Checking minimum RAM requirements

INFO Checking if Virtualization is enabled

INFO Checking if KVM is enabled

INFO Checking if libvirt is installed

INFO Checking if user is part of libvirt group

INFO Checking if active user/process is currently part of the libvirt group

INFO Checking if libvirt daemon is running

INFO Checking if a supported libvirt version is installed

INFO Checking if crc-driver-libvirt is installed

INFO Checking if systemd-networkd is running

INFO Checking if NetworkManager is installed

INFO Checking if NetworkManager service is running

INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists

INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists

INFO Checking if libvirt 'crc' network is available

INFO Checking if libvirt 'crc' network is active

CodeReady Containers requires a pull secret to download content from Red Hat.

You can copy it from the Pull Secret section of https://cloud.redhat.com/openshift/create/local.

? Please enter the pull secret **********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************

WARN Cannot add pull secret to keyring: failed to unlock correct collection '/org/freedesktop/secrets/collection/login'

INFO Loading bundle: crc_libvirt_4.7.11.crcbundle...

INFO Creating CodeReady Containers VM for OpenShift 4.7.11...

INFO Starting CodeReady Containers VM for OpenShift 4.7.11...

INFO CodeReady Containers instance is running with IP 192.168.130.11

INFO CodeReady Containers VM is running

INFO Generating new SSH Key pair...

INFO Updating authorized keys...

INFO Copying kubeconfig file to instance dir...

INFO Starting network time synchronization in CodeReady Containers VM

INFO Check internal and public DNS query...

INFO Check DNS query from host...

INFO Adding user's pull secret to instance disk...

INFO Verifying validity of the kubelet certificates...

INFO Starting OpenShift kubelet service

INFO Waiting for kube-apiserver availability... [takes around 2min]

INFO Adding user's pull secret to the cluster...

INFO Generating new password for the kubeadmin user

INFO Updating cluster ID...

INFO Starting OpenShift cluster... [waiting for the cluster to stabilize]

INFO 7 operators are progressing: authentication, dns, image-registry, network, openshift-controller-manager, ...

INFO 6 operators are progressing: authentication, dns, image-registry, network, openshift-controller-manager, ...

INFO 4 operators are progressing: authentication, image-registry, kube-apiserver, openshift-controller-manager

INFO 4 operators are progressing: authentication, image-registry, kube-apiserver, openshift-controller-manager

INFO 5 operators are progressing: authentication, image-registry, kube-apiserver, openshift-controller-manager, operator-lifecycle-manager-packageserver

INFO All operators are available. Ensuring stability...

ERRO Cluster is not ready: cluster operators are still not stable after 11m30.841378628s

INFO Adding crc-admin and crc-developer contexts to kubeconfig...

Started the OpenShift cluster.


The server is accessible via web console at:

  https://console-openshift-console.apps-crc.testing


Log in as administrator:

  Username: kubeadmin

  Password: RHWvU-6HoEU-7NqXQ-pgcNw


Log in as user:

  Username: developer

  Password: developer


Use the 'oc' command line interface:

  $ eval $(crc oc-env)

  $ oc login -u developer https://api.crc.testing:6443


No comments:

Post a Comment

PVC in terminating state

Referencee:https://veducate.co.uk/kubernetes-pvc-terminating/  I still had errors performing deployment, till I released that although I pre...