Need help to run CRC on Mac OS Sonoma (14.7.4 (23H420))

[bartalamu]

Hello to all, really looking for some gudes and help to make CRC working on my Mac.

MacOS:14.7.4 (23H420)
23.6.0 Darwin Kernel Version 23.6.0: Thu Dec 19 20:44:10 PST 2024; root:xnu-10063.141.1.703.2~1/RELEASE_ARM64_T6000 arm64

mac ~ % crc version
CRC version: 2.48.0+1aa46c
OpenShift version: 4.18.1
MicroShift version: 4.18.1

mac cache % crc config view

• consent-telemetry : no
• enable-cluster-monitoring : true
• memory : 16384
• pull-secret-file : ~/pull-secret.txt

bundle file: crc_vfkit_4.18.1_arm64.crcbundle

OCP is not able to fully start on CRC VM. Latest outputs and logs attached.
crc.log
case_attachment_1.txt

After attempts to start operator CRC automatically stoped.
INFO 5 operators are progressing: console, dns, image-registry, ingress, network

Thanks in advance!

[bartalamu]

Seems there are issue of starting all related MSes because of the CNI:
From the kubelet I see:
Network plugin returns error: no CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?"
pod="openshift-operator-lifecycle-manager/catalog-operator-7bc8c69474-jzlxz"

[core@crc net.d]$ pwd
/etc/kubernetes/cni/net.d
[core@crc net.d]$ sudo cat 00-multus.conf
[core@crc net.d]$ ls -l
total 0
-rw-------. 1 root root 0 Mar 18 07:49 00-multus.conf
drwxr-xr-x. 2 root root 60 Feb 24 09:39 whereabouts.d

[core@crc log]$ oc logs -n openshift-multus multus-7f4ts
2025-03-20T12:45:27+00:00 [cnibincopy] Successfully copied files in /usr/src/multus-cni/rhel9/bin/ to /host/opt/cni/bin/upgrade_a0178e05-15be-4fdb-95e2-8725980eecdc
2025-03-20T12:45:27+00:00 [cnibincopy] Successfully moved files in /host/opt/cni/bin/upgrade_a0178e05-15be-4fdb-95e2-8725980eecdc to /host/opt/cni/bin/
2025-03-20T12:45:27Z [verbose] multus-daemon started
2025-03-20T12:45:27Z [verbose] Readiness Indicator file check
2025-03-20T12:45:27Z [verbose] Readiness Indicator file check done!
I0320 12:45:27.439761 6906 certificate_store.go:130] Loading cert/key pair from "/etc/cni/multus/certs/multus-client-current.pem".
2025-03-20T12:45:27Z [error] failed to initialize the certificate manager: could not convert data from "/etc/cni/multus/certs/multus-client-current.pem" into cert/key pair: tls: failed to find any PEM data in certificate input
2025-03-20T12:45:27Z [error] error getting perNodeClient: failed to initialize the certificate manager: could not convert data from "/etc/cni/multus/certs/multus-client-current.pem" into cert/key pair: tls: failed to find any PEM data in certificate input
2025-03-20T12:45:27Z [panic] failed start the multus thick-plugin listener: failed to create the server: error getting perNodeClient: failed to initialize the certificate manager: could not convert data from "/etc/cni/multus/certs/multus-client-current.pem" into cert/key pair: tls: failed to find any PEM data in certificate input
2025-03-20T12:45:27Z [panic] ========= Stack trace output ========
2025-03-20T12:45:27Z [panic] Multus Panic
2025-03-20T12:45:27Z [panic] ========= Stack trace output end ========

Any guide how to fix it?

[cfergeau]

There seems to be multiple issues,

time="2025-03-19T12:02:25+02:00" level=info msg="5 operators are progressing: console, dns, image-registry, ingress, network"
time="2025-03-19T12:02:40+02:00" level=debug msg="Error: virtualization error: hypervisor virtualization error"

This one is quite bad because after this, the virtual machine CRC runs the cluster in no longer exists.

[cfergeau]

Can you provide more details about your hardware configuration? CPU model, memory, ...

[bartalamu]

I have fixed it but Will be great to make it working out of the box.
Issues was related to the multus certificate link - for some reasons i pointed to empty file:
[core@crc certs]$ ls -l
total 8
-rw-------. 1 root root 1143 Feb 23 08:34 multus-client-2025-02-23-08-34-33.pem
-rw-------. 1 root root 1135 Feb 24 09:12 multus-client-2025-02-24-09-12-16.pem
-rw-------. 1 root root 0 Mar 18 07:49 multus-client-2025-03-18-07-49-37.pem
lrwxrwxrwx. 1 root root 59 Mar 18 07:49 multus-client-current.pem -> /etc/cni/multus/certs/multus-client-2025-03-18-07-49-37.pem
[core@crc certs]$ sudo cat multus-client-current.pem

So I have relinked it to older ones which are OK:
[root@crc certs]# ln -s /etc/cni/multus/certs/multus-client-2025-02-24-09-12-16.pem multus-client-current.pem

No all staff is OK:
[core@crc certs]$ oc get po -A | grep multus
openshift-multus multus-additional-cni-plugins-rbbln 1/1 Running 5 2d5h
openshift-multus multus-admission-controller-7467cf9cf9-nnvcb 2/2 Running 0 6m21s
openshift-multus multus-tkvhb 1/1 Running 0 7m27s
openshift-multus network-metrics-daemon-c7fs5 2/2 Running 2 2d5h

Any thoughts WHY it like that put of the box?