Changing NFS service from NFSv4 to NFSv3 generates onscreen error
On screen error produced when changing from NFSv4 to NFSv3.
Steps to recreate:
1. Configure NFS service to use NFSv4 with NFSv3 ownership and save (see screenshot 1).
2. Re-Configuring NFS service to use NFSv3 generates onscreen error message on save (see screenshot 2).
Change from NFsv4 to NFSv3 in two stages. First unselect "NFSv3 ownership" and save as pure NFSv4. Second unselect NFSv4 and save again to get NFSv3.
#2 Updated by Erin Clark over 1 year ago
- Assignee changed from Erin Clark to William Grzybowski
William: this appears to be a middleware issue, I tried both the rest call which it is currently using and the websocket and neither would let me save without giving me this error message when I try to make both of these fields false.