http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c4 --- Comment #4 from Ancor Gonzalez Sosa --- See also this other related card https://trello.com/c/XQXJVOVl/242-port-yast-nfs-client-to-storage-ng But only partially related, since the problem here is not about adding the fstab entry (that works fine), but about mounting the share right away. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c6 Knut Alejandro Anderssen González changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |knut.anderssen@suse.com, | |nfbrown@suse.com Flags| |needinfo?(nfbrown@suse.com) --- Comment #6 from Knut Alejandro Anderssen González --- Neil, It seems we are not doing the automatically mount anymore after the service is started (Leap 15) https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0/nfs-utils/nf... https://build.opensuse.org/package/view_file/openSUSE:Leap:42.3/nfs-utils/nf... Could you take a look? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c8 --- Comment #8 from Knut Alejandro Anderssen González --- (In reply to Neil Brown from comment #7)

No, it doesn't really make sense for the nfs-client service to mount filesystems. systemd should do that directly. Whenever yast adds something to /etc/fstab it should "systemctl daemon-reload" so that the generators get run and systemd learns about the new contents of /etc/fstab. Do you see any problem with making yast do that?

I was already discussing with ancorgs about adopting that solution this time, so apparently shouldn't be any problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c24 José Iván López González changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jlopez@suse.com Resolution|--- |FIXED --- Comment #24 from José Iván López González --- (In reply to Neil Brown from comment #7)

No, it doesn't really make sense for the nfs-client service to mount filesystems. systemd should do that directly. Whenever yast adds something to /etc/fstab it should "systemctl daemon-reload" so that the generators get run and systemd learns about the new contents of /etc/fstab. Do you see any problem with making yast do that?

Using "systemctl daemon-reload" was tricky under certain scenarios (e.g., for a NFS share directly mounted by the user but not included in the fstab). Finally we have decided to delegate the mounting/unmounting actions to the yast storage stack. Thanks to that, now on the behavior is exactly the same when the nfs client is used standalone and when it is used through the Expert Partitioner. Fixed by yast2-storage-ng 4.2.73 and yast2-nfs-client 4.2.5. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c28 --- Comment #28 from Swamp Workflow Management --- 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=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c29 --- Comment #29 from Swamp Workflow Management --- 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.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c48 --- Comment #48 from Oliver Kurz --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/5619714 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c49 --- Comment #49 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/5714000 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed --- Comment #50 from Oliver Kurz --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/5714000 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c52 --- Comment #52 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/5875541 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c54 --- Comment #54 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/6092065 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c56 --- Comment #56 from Oliver Kurz --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/6296027 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c58 --- Comment #58 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/6515827 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c60 --- Comment #60 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/6900687 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c62 --- Comment #62 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/7162469 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c64 --- Comment #64 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/7438454 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c66 --- Comment #66 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/7676794 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c68 --- Comment #68 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/7849318 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c70 --- Comment #70 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/7959981 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c72 --- Comment #72 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/8122867 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c74 --- Comment #74 from openQA Review --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-nfs-client https://openqa.suse.de/tests/8380267 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 56 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.