search

nmaupu / freenas-provisioner

Kubernetes external provisioner using Freenas as backend
Apache License 2.0
132 stars 26 forks source link

Mount point not created when using Helm 3 #26

Closed zx1986 closed 4 years ago

zx1986 commented 5 years ago

Output of helm version:

version.BuildInfo{Version:"v3.0.0-beta.3", GitCommit:"5cb923eecbe80d1ad76399aee234717c11931d9a", GitTreeState:"clean", GoVersion:"go1.12.9"}

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T12:36:28Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}

Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:44:49Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): 

Self-hosting Kubernetes Cluster on DELL R930 Servers.

I am using Helm 2 install stable/redis-ha, and it works fine. But when I change the Helm 3, with same arguments, it faced:

MountVolume.SetUp failed for volume "pvc-d7ffe33c-d796-11e9-8568-801844f0932c" : 
mount failed: exit status 32 

Mounting command: systemd-run 
Mounting arguments: 
--description=Kubernetes transient mount for /var/lib/kubelet/pods/d802cecd-d796-11e9-8568-801844f0932c/volumes/kubernetes.io~nfs/pvc-d7ffe33c-d796-11e9-8568-801844f0932c 
--scope 
-- mount -t nfs 192.168.1.99:/mnt/data/super-kubernetes/my-space/data-redis-ha-server-0 /var/lib/kubelet/pods/d802cecd-d796-11e9-8568-801844f0932c/volumes/kubernetes.io~nfs/pvc-d7ffe33c-d796-11e9-8568-801844f0932c 

Output: 
Running scope as unit: run-r717513c4480b481ea2e4f0e3486caaeb.scope 
mount.nfs: 
access denied by server while mounting 192.168.1.99:/mnt/data/super-kubernetes/my-space/data-redis-ha-server-0

The PV and PVC was successful created on my FreeNAS just like I am using Helm 2. I am not sure if this a Helm 3 problem, but I works fine with Helm 2. I thought the key point maybe access denied by server while mounting ..., I had check the NFS services, and found that /mnt/data/super-kubernetes/my-space/data-redis-ha-server-0 did not exist at all.

Maybe the freenas-provisioner are not compatible with Helm 3?

travisghansen commented 5 years ago

I doubt it has anything to do helm 3. Did you repeat several times with 3 (completely deleting and recreating) and kept getting this issue?

maxirus commented 4 years ago

Can confirm that I am using Helm 3 and it deploys fine. Tested with both my PR and repo.

$ helm version
version.BuildInfo{Version:"v3.0.2", GitCommit:"19e47ee3283ae98139d98460de796c1be1e3975f", GitTreeState:"clean", GoVersion:"go1.13.5"}