You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microk8s seems to not install correctly
When I run "microk8s inspect" it complains about
Inspecting dqlite
Inspect dqlite
cp: cannot stat '/var/snap/microk8s/7394/var/kubernetes/backend/localnode.yaml': No such file or directory
What Should Happen Instead?
I am guessing the file should exist as it messes up the kubernetes network stack
Reproduction Steps
Issue happens on all out Azure vm's where we install microk8s with : snap install microk8s --classic
2. ...
Introspection Report
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/7394/var/kubernetes/backend/localnode.yaml': No such file or directory
Can you suggest a fix?
We manually do the following:
stop microk8s
create the file
chmod/chown the file correctly
start microk8s
Are you interested in contributing with a fix?
The text was updated successfully, but these errors were encountered:
Summary
Microk8s seems to not install correctly
When I run "microk8s inspect" it complains about
Inspecting dqlite
Inspect dqlite
cp: cannot stat '/var/snap/microk8s/7394/var/kubernetes/backend/localnode.yaml': No such file or directory
What Should Happen Instead?
I am guessing the file should exist as it messes up the kubernetes network stack
Reproduction Steps
Issue happens on all out Azure vm's where we install microk8s with : snap install microk8s --classic
2. ...
Introspection Report
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/7394/var/kubernetes/backend/localnode.yaml': No such file or directory
Can you suggest a fix?
We manually do the following:
Are you interested in contributing with a fix?
The text was updated successfully, but these errors were encountered: