Closed nouseforaname closed 8 months ago
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
Thanks, @nouseforaname
Our docs say that
3.0
is a valid nfs version. It turns out that this was undefined behavior in old versions of nfs-utils and will not work when the underlying CF Deployments runs on Jammy (as opposed to Xenial).Users have pointed reported: after updating the CF deployment from a xenial to a jammy stemcell, previously working volume services ( created with
version: 3.0
) stopped working. After updating their services to useversion: 3
keeping the rest of the configuration identical, the mounts succeeded again.The best proof for this change (without trying to track a commit in nfs-utils source), I could find is a comment by Steve Dickson (the maintainer) here: https://bugzilla.redhat.com/show_bug.cgi?id=1522633