search

kubernetes-sigs / nfs-ganesha-server-and-external-provisioner

NFS Ganesha Server and Volume Provisioner.
Apache License 2.0
413 stars 140 forks source link

error while mounting - 1 validation errors in block EXPORT #45

Closed samene closed 2 years ago

samene commented 3 years ago

PVC is not getting provisioned on some systems. It works on some and not on others. This is the error in the PVC

  Type     Reason              Age                    From                                                                                                                                           Message
  ----     ------              ----                   ----                                                                                                                                           -------
  Warning  ProvisioningFailed  6m4s                   mediation.apps.nfs.mycompany.nfs.provisioner.io_mediation-apps-nfs-mycompany-nfs-provisioner-66fd6b784-lp6dq_d33c2841-0caf-4b29-b087-61e3fbe9a24e  failed to provision volume with StorageClass "mediation-apps-nfs-mycompany-nfs-provisioner": error getting NFS server IP for volume: service SERVICE_NAME=mediation-apps-nfs-mycompany-nfs-provisioner is not valid; check that it has for ports map[{111 TCP}:true {111 UDP}:true {662 TCP}:true {662 UDP}:true {875 TCP}:true {875 UDP}:true {2049 TCP}:true {2049 UDP}:true {20048 TCP}:true {20048 UDP}:true {32803 TCP}:true {32803 UDP}:true] exactly one endpoint, this pod's IP POD_IP=10.42.0.151
  Normal   Provisioning        2m19s (x5 over 6m4s)   mediation.apps.nfs.mycompany.nfs.provisioner.io_mediation-apps-nfs-mycompany-nfs-provisioner-66fd6b784-lp6dq_d33c2841-0caf-4b29-b087-61e3fbe9a24e  External provisioner is provisioning volume for claim "mycompany-cloud/mediation-apps-nfs"
  Warning  ProvisioningFailed  2m19s (x4 over 5m49s)  mediation.apps.nfs.mycompany.nfs.provisioner.io_mediation-apps-nfs-mycompany-nfs-provisioner-66fd6b784-lp6dq_d33c2841-0caf-4b29-b087-61e3fbe9a24e  failed to provision volume with StorageClass "mediation-apps-nfs-mycompany-nfs-provisioner": error creating export for volume: error exporting export block
EXPORT
{
  Export_Id = 1;
  Path = /export/pvc-32c863f3-a086-4cc1-9e19-f809f41a8bec;
  Pseudo = /export/pvc-32c863f3-a086-4cc1-9e19-f809f41a8bec;
  Access_Type = RW;
  Squash = no_root_squash;
  SecType = sys;
  Filesystem_id = 1.1;
  FSAL {
    Name = VFS;
  }
}
: error calling org.ganesha.nfsd.exportmgr.AddExport: 0 export entries in /export/vfs.conf added because (export create, block validation) errors. Details:
Config File (/export/vfs.conf:54): 1 validation errors in block FSAL
Config File (/export/vfs.conf:54): Errors processing block (FSAL)
Config File (/export/vfs.conf:45): 1 validation errors in block EXPORT
Config File (/export/vfs.conf:45): Errors found in configuration block EXPORT
  Normal  ExternalProvisioning  6s (x26 over 6m18s)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "mediation.apps.nfs.mycompany.nfs.provisioner.io" or manually created by system administrator

Abd this is the error in the nfs pod

I0408 10:20:25.839702       1 main.go:65] Provisioner mediation.apps.nfs.mycompany.nfs.provisioner.io specified
I0408 10:20:25.839822       1 main.go:89] Setting up NFS server!
I0408 10:20:26.019674       1 server.go:149] starting RLIMIT_NOFILE rlimit.Cur 1048576, rlimit.Max 1048576
I0408 10:20:26.019702       1 server.go:160] ending RLIMIT_NOFILE rlimit.Cur 1048576, rlimit.Max 1048576
I0408 10:20:26.023483       1 server.go:134] Running NFS server!
E0408 10:20:31.139572       1 controller.go:908] error syncing claim "32c863f3-a086-4cc1-9e19-f809f41a8bec": failed to provision volume with StorageClass "mediation-apps-nfs-mycompany-nfs-provisioner": error getting NFS server IP for volume: service SERVICE_NAME=mediation-apps-nfs-mycompany-nfs-provisioner is not valid; check that it has for ports map[{111 TCP}:true {111 UDP}:true {662 TCP}:true {662 UDP}:true {875 TCP}:true {875 UDP}:true {2049 TCP}:true {2049 UDP}:true {20048 TCP}:true {20048 UDP}:true {32803 TCP}:true {32803 UDP}:true] exactly one endpoint, this pod's IP POD_IP=10.42.0.151
I0408 10:20:46.146203       1 provision.go:450] using service SERVICE_NAME=mediation-apps-nfs-mycompany-nfs-provisioner cluster IP 10.43.203.168 as NFS server IP
E0408 10:20:46.149486       1 controller.go:908] error syncing claim "32c863f3-a086-4cc1-9e19-f809f41a8bec": failed to provision volume with StorageClass "mediation-apps-nfs-mycompany-nfs-provisioner": error creating export for volume: error exporting export block
EXPORT
{
 Export_Id = 1;
 Path = /export/pvc-32c863f3-a086-4cc1-9e19-f809f41a8bec;
 Pseudo = /export/pvc-32c863f3-a086-4cc1-9e19-f809f41a8bec;
 Access_Type = RW;
 Squash = no_root_squash;
 SecType = sys;
 Filesystem_id = 1.1;
 FSAL {
  Name = VFS;
 }
}
: error calling org.ganesha.nfsd.exportmgr.AddExport: 0 export entries in /export/vfs.conf added because (export create, block validation) errors. Details:
Config File (/export/vfs.conf:54): 1 validation errors in block FSAL
Config File (/export/vfs.conf:54): Errors processing block (FSAL)
Config File (/export/vfs.conf:45): 1 validation errors in block EXPORT
Config File (/export/vfs.conf:45): Errors found in configuration block EXPORT

v3.0.0

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

boretom commented 3 years ago

Hi @samene, on what platform/hardware do you deploy it?

I tried to use it for a one-node homelab using Rancher and I didn't succeed (and ended up using the kvaps helm chart).

In my case the reason it most probably failed was because the pod is running on the docker overlay2 storage driver. And this doesn't allow "open_by_handle_at" calls, according to a comment on nfs-ganesha issue #511.

Config File (/export/vfs.conf:59): Errors found in configuration block EXPORT
)
30/07/2021 14:52:56 : epoch 61040e92 : nfs-provisioner-78659b8868-m5z7l : nfs-ganesha-20[dbus_heartbeat] vfs_lookup_path :FSAL :CRIT :Could not get handle for path /export/pvc-dbe7e85c-d788-4711-bb64-037f54ca8057, error Operation not supported
30/07/2021 14:52:56 : epoch 61040e92 : nfs-provisioner-78659b8868-m5z7l : nfs-ganesha-20[dbus_heartbeat] init_export_root :EXPORT :CRIT :Lookup failed on path, ExportId=2 Path=/export/pvc-dbe7e85c-d788-4711-bb64-037f54ca8057 FSAL_ERROR=(Operation not supported,95)
30/07/2021 14:52:56 : epoch 61040e92 : nfs-provisioner-78659b8868-m5z7l : nfs-ganesha-20[dbus_heartbeat] release_posix_file_system :FSAL :WARN :Filesystem /export is still claimed
30/07/2021 14:52:56 : epoch 61040e92 : nfs-provisioner-78659b8868-m5z7l : nfs-ganesha-20[dbus_heartbeat] gsh_export_addexport :EXPORT :CRIT :0 export entries in /export/vfs.conf added because (invalid param value) errors
30/07/2021 14:52:56 : epoch 61040e92 : nfs-provisioner-78659b8868-m5z7l : nfs-ganesha-20[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (AddExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidFileContent), message = (0 export entries in /export/vfs.conf added because (invalid param value) errors. Details:
Config File (/export/vfs.conf:59): 1 validation errors in block EXPORT
Config File (/export/vfs.conf:59): Errors found in configuration block EXPORT)
k8s-triage-robot commented 3 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner/issues/45#issuecomment-929379156): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.