Bug 1187722 - YaST2 NFS Server and Client configuration modules can't configure firewall and Client has trouble w/ NFSv4
YaST2 NFS Server and Client configuration modules can't configure firewall an...
Status: NEW
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2
Leap 15.3
x86-64 openSUSE Leap 15.3
: P5 - None : Normal (vote)
: ---
Assigned To: YaST Team
Jiri Srain
https://trello.com/c/QEg5uZgz
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-06-25 14:42 UTC by T. Lee Davidson
Modified: 2021-06-28 06:02 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description T. Lee Davidson 2021-06-25 14:42:26 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Build Identifier: 

The YaST2 NFS Server and Client configuration modules fail to configure a working share without additional knowledge the average user may not have.

The Server Configuration module thinks that a 'nfs-kernel-server' service is required to configure the firewall; leading to a failed configuration unless the user knows to simply add the 'nfs' service in the firewall.

https://ibb.co/c2qd2s9

The Client Configuration module reports that the 'nfs' service is not available to configure the firewall -- when it is available.

https://ibb.co/mCmNHRH

And, with the server set to serve pure NSFv4, the Client module fails to find any networked shares from the scan operation. The Client module will find exported shares on the host only when the host address is manually entered and the NSF Version is set to "Force NSFv4".


Reproducible: Always

Steps to Reproduce:
On the server:
1. With nfs-kernel-server installed, launch the YaST2 NFS Server module.
2. See the message "Firewall not configurable..."
3. Finish exporting the share anyway.
4. Manually add the 'nfs' service to the appropriate zone in the firewall and reload it.

On the client:
1. Launch the YaST2 NFS Client module.
2. Go to the NFS Settings tab.
3. See the message "Firewall not configurable..."
4. Manually add the 'nfs' service to the appropriate zone in the firewall and reload it.

5. Go back to the NFS Shares tab in NFS Client configuration.
6. Click Add
7. Click Choose.
8. See the error message that no NFS server was found.

9. Set NFS Version to "Force NSFv4".
10. Click Choose.
11. Again, see the error message that no NFS server was found.

12. Manually enter the host address.
13. Click Select.
14. Now see the exported directories.

15. Set NFS Version back to "Any (Highest Available)".
16. Click Select.
17. Now see that the exported directories list is empty.
Actual Results:  
The exported share could not be served without manually configuring the server's firewall.

The exported share could not be found by the client without manually configuring the client's firewall, manually entering the server's address, and forcing the client to NSFv4.

Expected Results:  
I expected that the NFS Server configuration would be able to configure the firewall without me having to know that the firewall 'nfs-kernel-server' service is not required, but that the 'nfs' service is and must be manually allowed.

I expected that the NFS Client configuration would be able to configure the firewall, would find the available exported directory from the scanning operation, and would allow me to proceed with adding the share intuitively, ie. choose the server, select the exported share, specify the mount point, and Add it.
Comment 1 Imobach Gonzalez Sosa 2021-06-28 06:02:19 UTC
Hi,

Summarizing, there are several problems here:

* The server module still relies on an nfs-kernel-server firewall service which, actually, does not exist anymore.
* The client module reports that the firewall 'nfs' service does not exist (but it does).
* When the server is set to pure NFSv4, the client fails to find the shares.

OK, usually we ask for YaST2 logs, but in this case I think that the issue is easy to reproduce.

Thanks for reporting. We are moving this bug the our SCRUM queue.

Regards,
Imo