Not really a bug, perhaps?
Scenario:
NFS enabled with NFSv4 checked
NFS IP filtering enabled
Attempt to mount NFS mount from a VM with a non-whitelisted IP address
NFS mount is successful, but results in input/output error when attempting to read the files within the mounted directory
With NFSv3, it's obvious that you are blocked because of the "connection refused" error. With NFSv4, it's not obvious at all what's happening. This was frustrating to troubleshoot because I forgot the IP change I made. Obviously that's my fault, but figured I'd mention it here in case this should be designed to block the mount entirely similar to NFSv3.
Scenario:
NFS enabled with NFSv4 checked
NFS IP filtering enabled
Attempt to mount NFS mount from a VM with a non-whitelisted IP address
NFS mount is successful, but results in input/output error when attempting to read the files within the mounted directory
With NFSv3, it's obvious that you are blocked because of the "connection refused" error. With NFSv4, it's not obvious at all what's happening. This was frustrating to troubleshoot because I forgot the IP change I made. Obviously that's my fault, but figured I'd mention it here in case this should be designed to block the mount entirely similar to NFSv3.