NFS share does not mount after TAS upgrade
Article ID: 297531
Updated On:
Products
VMware Tanzu Application Service for VMs
Issue/Introduction
After the upgrade to TAS versions 5.0.7, 4.0.17 or 2.13.35 which all include nfs-release-version 7.1.47, any nfs share mounted with version 3.0 will not be able to mount.
Earlier versions of nfs-utils handled specifying mount -t nfs -o vers=3.0. This apparently was undesired behavior since there aren't any minor versions with NFS v3.
If the share was mounted with "vers=3" will not be impacted by this issue.
Earlier versions of nfs-utils handled specifying mount -t nfs -o vers=3.0. This apparently was undesired behavior since there aren't any minor versions with NFS v3.
If the share was mounted with "vers=3" will not be impacted by this issue.
Resolution
Currently there is no resolution.
As workaround, the share will need to be mounted with "vers=3", then re-bind apps to the new mount. Valid values are 3, 4.0, 4.1 or 4.2. See TAS documentation.
As workaround, the share will need to be mounted with "vers=3", then re-bind apps to the new mount. Valid values are 3, 4.0, 4.1 or 4.2. See TAS documentation.
cf create-service nfs Existing SERVICE-INSTANCE-NAME -c ‘{“share”:“SERVER/SHARE”, “version”:“NFS-PROTOCOL”}’
Feedback
Yes
No
Powered by
