What were you trying to do that didn't work?

The NFS server behaves different depending on whether you enable/disable `vers4` in combination with other parameters. In some cases, `vers4=n` disables all NFSv4 versions, in other cases it doesn't.

Examples

With the following settings, the service starts, and the client can mount the share with version 3, 4.1, and 4.2:

vers3=y
vers4=n
vers4.0=n
vers4.1=y
vers4.2=y

With the following settings, the service starts but clients can only mount with v3:

vers3=y
vers4=n
#vers4.0=n
#vers4.1=y
#vers4.2=y

With the following settings, the `nfs-server` service fails to start (because no protocol version is enabled in the backend):

vers3=n
vers4=n
vers4.0=n
vers4.1=y
vers4.2=y

Please provide the package NVR for which bug is seen:

RHEL 8.9: nfs-utils-2.3.3-59.el8.x86_64

RHEL 9.3: nfs-utils-2.5.4-20.el9.x86_64

How reproducible:

Always