NFS Services Start Script should Retry

[pwschuurman]

Currently the NFS Services Start script does not retry on failure: https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/blob/518f22d7e0edae391e321e312a870daa70856263/deploy/kubernetes/nfs_services_start.sh, and sleeps at the end of execution.

It should either retry running rpc.statd service, NFS services, or exit with a non-zero code on failure. The latter would enable the script to be restarted in a Kubernetes environment.

[pwschuurman]

rpc.statd could be checked by adding the following validation after nfs-common service is started.

if ! pidof rpc.statd >/dev/null
then
    echo "rpc.statd not running"
    exit 3
fi

Trying out service nfs-common status, the status check fails after successful service nfs-common start. It seems that rpc.idmapd is started opportunistically (eg: ignored when starting), but status checking is strict. Running service nfs-common start succeeds:

# service nfs-common start
Starting NFS common utilities: statd.
# echo $?
0

However running status fails:

# service nfs-common status
rpc.idmapd not running
# echo $?
3

[k8s-triage-robot]

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

This bot triages un-triaged issues 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten