tanzu will sometimes fail to start when $HOME is mounted to a NFS share with locking disabled

[carlosonunez-vmw]

Bug description

tanzu sometimes fails with EBADF when $HOME is mounted to a NFS share.

No tanzu CLI commands work when this occurs.

Affected product area (please put an X in all that apply)

• ( ) APIs
• ( ) Addons
• (X) CLI
• ( ) Docs
• ( ) IAM
• ( ) Installation
• ( ) Plugin
• ( ) Security
• ( ) Test and Release
• ( ) User Experience
• ( ) Developer Experience

Expected behavior

tanzu --version (or any tanzu command) works

Steps to reproduce the bug

1. Create a new home directory
2. Mount an NFSv4 share to that home directory as rw with nolock
3. Create a new user and set its home directory to that path.
4. Create a login shell as that user
5. Run any tanzu command.

Version (include the SHA if the version is not obvious)

Environment where the bug was observed (cloud, OS, etc)

RHEL7 machine

Relevant Debug Output (Logs, manifests, etc)

Additional Notes

I noticed that the file locking behavior happens here. Would it be possible to detect whether HOME is mounted on a NFS share and has locking disabled?

[github-actions]

Hey @carlosonunez-vmw! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Tanzu Framework.