Problems detected in kubelet

[fdiprete]

What Happened?

$ minikube start
😄 minikube v1.33.1 on Fedora 39
✨ Using the qemu2 driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🏃 Updating the running qemu2 "minikube" VM ...
🐳 Preparing Kubernetes v1.30.0 on Docker 26.0.2 ...
🤦 Unable to restart control-plane node(s), will reset cluster:
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
❗ Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error listing StorageClasses: Get "https://localhost:46303/apis/storage.k8s.io/v1/storageclasses": dial tcp [::1]:46303: connect: connection refused]
🌟 Enabled addons: storage-provisioner
❌ Problems detected in kubelet:

Attach the log file

minikube.log

Operating System

Redhat/Fedora

Driver

QEMU

[kundan2707]

/kind support

[kundan2707]

@fdiprete there are many QEMU related siisye reported here. #14146

[kundan2707]

QEMU with linix is not tested completly and its not preferable to use.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale