http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c8 José Iván López González <jlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from José Iván López González <jlopez@suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #6)
Let me recap all this:
1) The usage of "nfs-server" instead of "nfsserver" was already implemented more than one year ago in the scope of bug#1116779.
2) Regarding "nfs-client.target" vs "nfs", we will change the approach used by yast2-nfs-client in SLE-15-SP1 and subsequent versions. The YaST module will not longer rely in any external service/target/unit/whatever to mount and umount the NFS shares. So there is nothing to fix here because the name will not be relevant anymore. See https://github.com/yast/yast-nfs-client/pull/89
Regarding this point, mounting/unmounting actions are now delegated to the yast storage stack (fixed by yast2-storage-ng 4.2.73 and yast2-nfs-client 4.2.5). See [1, 2] for more details. [1] https://bugzilla.suse.com/show_bug.cgi?id=1006815#c24 [2] https://bugzilla.suse.com/show_bug.cgi?id=1151426#c9
3) There is another bug report related to (1) about managing the service when kerberos is enabled. That's fixed by https://github.com/yast/yast-nfs-server/pull/41
When all that is merged, we could close this bug.
-- You are receiving this mail because: You are on the CC list for the bug.