microk8s node is not in ready state

[tbhagwat16]

Summary

microk8s node is not in ready state

What Should Happen Instead?

I have installed microk8s and when I have checked the node it is in not ready state.

Reproduction Steps

1. Install microk8s on redhat
2. Start the microk8s
3. node is in notready state

Introspection Report

[root@tejshri-test3 learn-vault-secrets-operator]# microk8s inspect
Inspecting system
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-kubelite is running
  Service snap.microk8s.daemon-k8s-dqlite is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy openSSL information to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy asnycio usage and limits to the final report tarball
  Copy inotify max_user_instances and max_user_watches to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting dqlite
  Inspect dqlite
cp: cannot stat '/var/snap/microk8s/8511/var/kubernetes/backend/localnode.yaml': No such file or directory

Building the report tarball
  Report tarball is at /var/snap/microk8s/8511/inspection-report-20251201_050456.tar.gz

Can you suggest a fix?

Are you interested in contributing with a fix?

yes

[sibelius]

without this localnode.yaml you need to reset the cluster