install karmada with “karmadactl init --etcd-storage-mode PVC --storage-classes-name {StorageClassesName}“ doesn't work

[sawchen]

What happened: my k8s version is 1.27.6，now i want to install karmada with the command “karmadactl init --etcd-storage-mode PVC --storage-classes-name nfs-client“ but kubelet reported the error like this

it seems the PVC can not be created successfully the storageclasses is nfs server，and I check that storage-classes is healthly which I used it to helm install a mariadb service.

this is my storage-class info

What you expected to happen: how can i fix the problem. i want to use highly available(HA) feature, like use arg ”karmadactl init --karmada-apiserver-replicas 3 --etcd-replicas 3 --etcd-storage-mode PVC --storage-classes-name {StorageClassesName}“ How to reproduce it (as minimally and precisely as possible): install nfs-subdir-external-provisioner with helm

and then install karmada with “karmadactl init --etcd-storage-mode PVC --storage-classes-name {StorageClassesName}“ Anything else we need to know?:

Environment:

• Karmada version:1.7.1
• kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
• Others:k8s version 1.27.6
• nfs-subdir-external-provisioner v4.0.2

[RainbowMango]

cc @chaosi-zju for help

[chaosi-zju]

/assign

[chaosi-zju]

@sawchen Hi, I think you can first check your environment by following steps:

1. check if /nvdata/nv-nfs dir exist in your node which installed nfs server (may be node 10.30.60.13)
2. check if nfs server run normal, you can execute mount -t nfs 10.30.60.13:/nvdata/nv-nfs ~/nvdata -o nolock to see whether mount success

[chaosi-zju]

@sawchen I have tested too, and success:

from the error log you provided, it is more likely due to you nfs server dir /nvdata/nv-nfs not exist