[Bug 1218158] [usr-merge] yast-nfs-(server|client) hardcoded configuration file /etc/idmapd.conf
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1218158
https://bugzilla.suse.com/show_bug.cgi?id=1218158#c15
Fabian Vogt
Ana, please, don't be blocked by YaST here. Just release it. If someone uses YaST and it's broken we'll find out later. The YaST NFS Server has lower priority than other team tasks now.
openQA tests yast nfs server and client modules and that test fails, so it's not possible to "just release it", something needs to be done explicitly. (In reply to Stefan Hundhammer from comment #10)
But it's indeed a good question how useful those YaST modules are these days, both yast2-nfs-server and yast2-nfs-client. They will both need quite some changes for the usr-merge:
src/yast 81 % grep -E 'SCR\.(Read|Write).*etc' yast-nfs-*/**/*.rb | sed -e 's/^/> /'
yast-nfs-client/src/modules/Nfs.rb: Convert.to_string(SCR.Read(path(".etc.idmapd_conf.value.General.Domain"))) yast-nfs-client/src/modules/Nfs.rb: SCR.Write(path(".etc.idmapd_conf.value.General.Domain"), @idmapd_domain) yast-nfs-client/src/modules/Nfs.rb: SCR.Write(path(".etc.idmapd_conf"), nil) yast-nfs-server/src/include/nfs_server/ui.rb: SCR.Read(path(".etc.idmapd_conf.value.General.Domain")) yast-nfs-server/src/modules/NfsServer.rb: SCR.Read(path(".etc.exports")), yast-nfs-server/src/modules/NfsServer.rb: SCR.Read(path(".etc.idmapd_conf.value.General.Domain")) yast-nfs-server/src/modules/NfsServer.rb: if !SCR.Write(path(".etc.exports"), @exports) yast-nfs-server/src/modules/NfsServer.rb: if !SCR.Write(path(".etc.idmapd_conf.value.General.Domain"), @domain) || yast-nfs-server/src/modules/NfsServer.rb: !SCR.Write(path(".etc.idmapd_conf"), nil)
For yast-nfs-server: /etc/exports didn't change, for /etc/idmapd.conf it apparently only reads the domain which has "localdomain" as default in /usr/etc anyway, so the hardcoded fallback is fine. Just the dialog is a bit annoying and misleading. Only theoretical issue is with writing. FWICT it would only write [General] Domain and not the other entries, but as the other values are defaults anyway that probably doesn't matter. For yast-nfs-client there's no hardcoded default, FWICT it would try to write nil into ".etc.idmapd_conf.value.General.Domain". Not sure what effect that has. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com