VMs go readonly after being created. NFSv4 Incremental

Issue

- VMs go readonly after being created.

- the lvdisplay command will show that newly created LVM partitions are NOT available.

- the newly created VMs will show up in read-only mode even though everything is fine with the template.

Environment

OnApp 5.x.x

NFS 4

Static and cloud-boot environments

NFS mounts on HVs and Backup servers:

/onapp/backups /onapp/templates

Resolution

Use NFS3 instead of NFS4.

How to switch back to NFSv3:

1) ssh to the Hypervisor in question

2) check your currently mounted devices by running the command: mount

3) as you can see, the version in use is version 4 (vers\):

377.235.95.01:/onapp/backups on /onapp/backups type nfs (rw,vers=4,addr=377.235.95.01)

4) To switch these over to NFSv3, you would simply run this command:

mount -o vers=3 nfs/path /directory

Note: replace nfs/path and /directory with the correct information needed. So using the example above, we would run the command like this:

mount -o vers=3 377.235.95.01:/onapp/templates /onapp/backups

5) Once you have done this, run the mount command to make sure the NFS mount has changed versions successfully. You should see something like this:

377.235.95.01:/onapp/backups on /onapp/backups type nfs (rw,vers=3,addr=377.235.95.01)

Cause

As of OnApp 5.0, and all earlier versions, NFS version 4 is still not supported with our current layout due to some incompatibilities regarding attributes, permissions, etc. We recommend using NFS version 3.

This is because nfsv4 does some extra attr checks on files, so when OnApp tries to mount the filesystem, it doesn't have the right attributions/permissions.

 377.235.95.01:/onapp/templates on /onapp/templates type nfs (rw,vers=4,addr=377.235.95.01)