Describe the bug a clear and concise description of what the bug is.
If the /home
directory is not exported on the NFS Server then the pod will not create correctly and will stay pending.
What's your helm version?
version.BuildInfo{Version:"v3.7.2", GitCommit:"663a896f4a815053445eec4153677ddc24a0a361", GitTreeState:"clean", GoVersion:"go1.16.10"}
What's your kubectl version?
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3", GitCommit:"816c97ab8cff8a1c72eccca1026f7820e93e0d25", GitTreeState:"clean", BuildDate:"2022-01-25T21:25:17Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.7-eks-4721010", GitCommit:"b77d9473a02fbfa834afa67d677fd12d690b195f", GitTreeState:"clean", BuildDate:"2022-06-27T22:19:07Z", GoVersion:"go1.17.10", Compiler:"gc", Platform:"linux/amd64"}
Which chart?
viya4-home-dir-builder
What's the chart version?
0.2.2
What happened?
Pod times out with the error:
Unable to attach or mount volumes: unmounted volumes=[userhome], unattached volumes=[userhome scripts kube-api-access-f57qh]: timed out waiting for the condition
What you expected to happen?
No response
How to reproduce it?
Use a newly created EFS in AWS. Use this as the NFS Server parameter.
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
helm install viya4-demo-homedir-builder selerity/viya4-home-dir-builder --version 0.2.2 -nviya4-demo-viya --set viya.base_url=https://viya.sascloud.com.au --set nfs.server=10.5.0.217
kubectl -nviya4-demo-viya create job --from=cronjob/viya4-demo-homedir-builder-viya4-home-dir-builder test
Anything else we need to know?
No response