RHEL7.6 NFS4.0 client LOCK with new_lock_owner=1 request receives NFS4ERR_BAD_SEQID from NetApp filer after RELEASE_LOCKOWNER with same lock_owner4

Issue

• OpenStack hypervisors on which they are not able to launch a qemu VM from those images which are located on NetApp NFSv4 share and have hw_disk_bus defined as 'scsi' and hw_scsi_model as 'virtio-scsi'. Getting the error below showing a qemu-kvm process with a "Failed to lock byte" error similar to the following

2019-06-20 10:41:54.144 1 ERROR nova.compute.manager [instance: de70f738-4293-4660-bbdf-e2c41ec2180a] libvirtError: internal error: qemu unexpectedly closed the monitor: 2019-06-20T08:41:53.397923Z qemu-kvm: -drive file=/var/lib/nova/instances/de70f738-4293-4660-bbdf-e2c41ec2180a/disk,format=qcow2,if=none,id=drive-scsi0-0-0-0,cache=none: Failed to lock byte 100
2019-06-20 10:41:54.144 1 ERROR nova.compute.manager [instance: de70f738-4293-4660-bbdf-e2c41ec2180a]
2019-06-20 10:41:54.203 1 INFO nova.compute.manager [req-afe249a8-8737-4a69-b4d4-70dcab6f7749 fa0f3e24b251482fa042c786a63f51de ac0b905d98b448a5a966a193411790fa - default default] [instance: de70f738-4293-4660-bbdf-e2c41ec2180a] Terminating instance
2019-06-20 10:41:54.211 1 INFO nova.virt.libvirt.driver [-] [instance: de70f738-4293-4660-bbdf-e2c41ec2180a] Instance destroyed successfully.

• Unable to launch a qemu VM located at Netapp (nfsv4) through 'virtio-scsi' however can create new VM's on the same hypervisor from the images through 'virtio-blk'

• The issue gets resolved after the compute node is rebooted after that they can spawn VM's through 'virtio-scsi' and 'virtio-blk '

• When this issue occurs NFS related error messages 'NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff968373a98020!' are logged

   2019-06-06 20:43:36 +02:00 nodename kern.warning kernel: [5470403.042351] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff9a60fd34b020!
   2019-06-06 20:43:36 +02:00 nodename kern.warning kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff9a60fd34b020!