[Bug 1060159] New: yast2-nfs-server and yast2-nfs-client should use the same service names as upstream nfs-utils
http://bugzilla.suse.com/show_bug.cgi?id=1060159 Bug ID: 1060159 Summary: yast2-nfs-server and yast2-nfs-client should use the same service names as upstream nfs-utils Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: nfbrown@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Upstream nfs-utils uses "nfs-server.service" to manage the nfs server and related services and "nfs-client.target" to manage nfs client services. SUSE traditionally used "nfsserver" and "nfs" for these, and yast2 still uses these names. nfs-utils for suse provides gateway services (nfs.service and nfsserver.service) which attempts to allow the old names to work transparently, but this is error prone and not a good long term solution. It would be good to deprecate the old names and standardize on the upsrteam names. One part of this is to change yast2-nfs-server and yast2-nfs-client to use the new names. This will work one any release since SLE12-SP2. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c1 José Iván López González <jlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez@suse.com, | |nfbrown@suse.com Flags| |needinfo?(nfbrown@suse.com) --- Comment #1 from José Iván López González <jlopez@suse.com> --- Yes, although the names could be error prone, IMHO this is closest to a FATE than a bug. What do you think? In case you agree, maybe the most proper stream could be to create a FATE. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igonzalezsosa@suse.com Assignee|yast2-maintainers@suse.de |igonzalezsosa@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c2 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nfbrown@suse.com) | --- Comment #2 from Neil Brown <nfbrown@suse.com> ---
maybe the most proper stream could be to create a FATE.
Maybe. For something as easy to implement as this, I personally prefer bugzilla, but as I won't be implementing it, that probably isn't relevant. I'll leave it up to the Yast2 team - if they refer a FATE, I'm happy to support that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c3 José Iván López González <jlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #3 from José Iván López González <jlopez@suse.com> --- Yes, you are right. In this case a FATE is too much. Imobach is already working on this improvement. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c4 Christopher Hofmann <cwh@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrivrain@suse.com --- Comment #4 from Christopher Hofmann <cwh@suse.com> --- *** Bug 1157892 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c5 Christopher Hofmann <cwh@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |CONFIRMED URL| |https://trello.com/c/ci7mFs | |V9/3732-tw-p4-1157892-unabl | |e-to-mount-the-nfs-entries- | |from-etc-fstab-no-nfsservic | |e-file CC| |cwh@suse.com, | |yast-internal@suse.de Assignee|igonzalezsosa@suse.com |yast-internal@suse.de Flags| |needinfo?(yast-internal@sus | |e.de) --- Comment #5 from Christopher Hofmann <cwh@suse.com> --- Imo, you set this to "IN PROGRESS" - are you working on this? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(yast-internal@sus | |e.de) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c6 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com --- Comment #6 from Ancor Gonzalez Sosa <ancor@suse.com> --- 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 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.
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.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:13895:moderate -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c10 --- Comment #10 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2020:0530-1: An update that has 6 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1006815,1060159,1149754,1151426,1156446,1161687 CVE References: Sources used: SUSE Linux Enterprise Module for Open Buildservice Development Tools 15-SP1 (src): libstorage-ng-4.1.107-4.11.8 SUSE Linux Enterprise Module for Development Tools 15-SP1 (src): libstorage-ng-4.1.107-4.11.8 SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): libstorage-ng-4.1.107-4.11.8, yast2-nfs-client-4.1.8-3.7.7, yast2-storage-ng-4.1.91-3.19.15 SUSE Linux Enterprise Installer 15-SP1 (src): libstorage-ng-4.1.107-4.11.8, yast2-storage-ng-4.1.91-3.19.15 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 Maintenance Robot <maint-coord+maintenance_robot@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:13895:moderate | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1060159 http://bugzilla.suse.com/show_bug.cgi?id=1060159#c11 --- Comment #11 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-RU-2020:0306-1: An update that has 6 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1006815,1060159,1149754,1151426,1156446,1161687 CVE References: Sources used: openSUSE Leap 15.1 (src): libstorage-ng-4.1.107-lp151.3.9.1, yast2-nfs-client-4.1.8-lp151.2.3.1, yast2-storage-ng-4.1.91-lp151.2.12.1 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com