nfs fails to mount when using ubuntu jammy stemcells

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Existing and/or new apps bound to nfs service crash with the following error seen in app logs

App instance exited with guid 11111111-2222-3333-4444-555555555555 payload: {"instance"=>"xxxxxx-xxxx-xxxx-xxxx-xxxx", "index"=>0, "cell_id"=>"1e5gg9d8-e59n-01bp-1490-5nw3a13eah20", "reason"=>"CRASHED

We also observe errors in Diego cell logs indicating that the volume failed to mount

App instance exited with guid 11111111-2222-3333-4444-555555555555 payload: {"instance"=>"xxxxxx-xxxx-xxxx-xxxx-xxxx", "index"=>0, "cell_id"=>"1e5gg9d8-e59n-01bp-1490-5nw3a13eah20", "reason"=>"CRASHED", "exit_description"=>"failed to mount volume, errors: exit status 32", "crash_count"=>13,

TAS versions prior to 3.0 deploy with ubuntu-xenial stemcells and support specifying nfs protocol minor version 3.x. TAS 3.0+ deploys with ubuntu-jammy stemcell and does not utilize a minor version. This causes a change in the nfs volume service mount.

Environment

Product Version: 3.0

Resolution

When creating the nfs volume service, the nfs protocol will need to omit the minor version and change from 3.0 to 3 as shown below.

cf create-service nfs Existing SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE", "version":"3"}'