MountVolume.SetUp failed for all volumes
See original GitHub issueUpon inspecting any pod, I get an error like the following
MountVolume.SetUp failed for volume "kube-dns-token-5nbrm" : couldn't propagate object cache: timed out waiting for the condition
Please run microk8s.inspect
and attach the generated tarball to this issue.
inspection-report-20191015_164003.tar.gz
We appreciate your feedback. Thank you for using microk8s.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
MountVolume.SetUp failed for volume "kube-api-access ...
What happened: Cannot mount kube-root-ca.crt when in a kind cluster with three worker nodes. I also have problems setting up pods (crash ->...
Read more >`MountVolume.SetUp failed for volume` due to multipathd on ...
Details. This is caused by multipath creating a multipath device for any eligible device path including every Longhorn volume device not explicitly blacklisted....
Read more >FailedMount MountVolume.SetUp failed for volume "kube-api ...
Bug 1999325 - FailedMount MountVolume.SetUp failed for volume "kube-api-access" : object "openshift-kube-scheduler"/"kube-root-ca.crt" not registered.
Read more >MountVolume.SetUp failed for volume "data" : hostPath type ...
You can add a volumeMounts inside your container: containers: - name: increase-fd-ulimit volumeMounts: - name: data mountPath: ...
Read more >MountVolume.SetUp failed for volume pvc, mount failed:
[root@masternode ~]# systemctl status nfs-server ○ nfs-server.service - NFS server and services Loaded: loaded ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This seems to have resolved itself after a clean remove and reinstall.
EDIT: Nvm. The issue seems to happen when I install rbac first.
Repro: 1) install fresh microk8s with channel=1.15/stable. 2) microk8s.enable rbac, then microk8s.enable storage.
You’ll get the above error. However, if I do microk8s.enable storage first, the host provisioner comes up just fine. Bizarre
result
result
Everything works fine. Something about microk8s.enable rbac is screwing everything up.