http://bugzilla.suse.com/show_bug.cgi?id=1006815
Bug ID: 1006815 Summary: [Build 20161024] yast2 nfs-client does not mount added export Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: jpupava@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: ---
Created attachment 699166 --> http://bugzilla.suse.com/attachment.cgi?id=699166&action=edit y2logs
### observed nfs client does not mount added export, nfs client configuration is ok and the export is added in fstab, nfs client service is running but export is not mounted
https://openqa.opensuse.org/tests/289982#step/yast2_nfs_client/14
### workaround mount -a does mount nfs export
### expected added export should be also mounted
linux-2cg7:~ # systemctl status nfs-client.target ● nfs-client.target - NFS client services Loaded: loaded (/usr/lib/systemd/system/nfs-client.target; disabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-client.target.d └─nfs.conf Active: active since Tue 2016-10-25 09:36:52 EDT; 36s ago
Oct 25 09:36:52 linux-2cg7 systemd[1]: Reached target NFS client services. linux-2cg7:~ # linux-2cg7:~ # systemctl show nfs.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath MainPID=0 Id=nfs.service Description=Alias for NFS client LoadState=loaded ActiveState=active SubState=exited FragmentPath=/usr/lib/systemd/system/nfs.service UnitFileState=enabled linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) linux-2cg7:~ # linux-2cg7:~ # grep nfs /etc/fstab localhost:/tmp/nfs/server /tmp/nfs/client nfs defaults 0 0 linux-2cg7:~ # linux-2cg7:~ # mount -a linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) localhost:/tmp/nfs/server on /tmp/nfs/client type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=::1,local_lock=none,addr=::1) linux-2cg7:~ #
http://bugzilla.suse.com/show_bug.cgi?id=1006815
Ancor Gonzalez Sosa ancor@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com Assignee|yast2-maintainers@suse.de |ancor@suse.com
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 ancor@suse.com --- 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.
http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c5
Knut Alejandro Anderssen González knut.anderssen@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mloviska@suse.com
--- Comment #5 from Knut Alejandro Anderssen González knut.anderssen@suse.com --- *** Bug 1090886 has been marked as a duplicate of this 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 knut.anderssen@suse.com 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 knut.anderssen@suse.com --- 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?
http://bugzilla.suse.com/show_bug.cgi?id=1006815 http://bugzilla.suse.com/show_bug.cgi?id=1006815#c7
Neil Brown nfbrown@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nfbrown@suse.com) |
--- Comment #7 from Neil Brown nfbrown@suse.com --- 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?
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 knut.anderssen@suse.com --- (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.
http://bugzilla.suse.com/show_bug.cgi?id=1006815
Arvin Schnell aschnell@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com
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 jlopez@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jlopez@suse.com Resolution|--- |FIXED
--- Comment #24 from José Iván López González jlopez@suse.com --- (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.
http://bugzilla.suse.com/show_bug.cgi?id=1006815
Swamp Workflow Management swamp@suse.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:13895:moderate
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 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.
http://bugzilla.suse.com/show_bug.cgi?id=1006815
Maintenance Robot maint-coord+maintenance_robot@suse.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:13895:moderate |
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 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
http://bugzilla.suse.com/show_bug.cgi?id=1006815
Martin Loviska mloviska@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|mloviska@suse.com |
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c48
--- Comment #48 from Oliver Kurz okurz@suse.com --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c49
--- Comment #49 from openQA Review openqa-review@suse.de --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c49
--- Comment #49 from openQA Review openqa-review@suse.de --- 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 okurz@suse.com --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c51
--- Comment #51 from openQA Review openqa-review@suse.de --- 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/5772057
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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c52
--- Comment #52 from openQA Review openqa-review@suse.de --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c53
--- Comment #53 from Oliver Kurz okurz@suse.com --- 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/5966081
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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c54
--- Comment #54 from openQA Review openqa-review@suse.de --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c55
--- Comment #55 from Oliver Kurz okurz@suse.com --- 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/6186349
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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c56
--- Comment #56 from Oliver Kurz okurz@suse.com --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c57
--- Comment #57 from openQA Review openqa-review@suse.de --- 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/6379577
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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c58
--- Comment #58 from openQA Review openqa-review@suse.de --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c59
--- Comment #59 from openQA Review openqa-review@suse.de --- 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/6660083
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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c60
--- Comment #60 from openQA Review openqa-review@suse.de --- 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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c61
--- Comment #61 from openQA Review openqa-review@suse.de --- 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/7020588
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
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c62
--- Comment #62 from openQA Review openqa-review@suse.de --- 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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c63
--- Comment #63 from openQA Review openqa-review@suse.de --- 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/7296943
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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c64
--- Comment #64 from openQA Review openqa-review@suse.de --- 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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c65
--- Comment #65 from openQA Review openqa-review@suse.de --- 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/7571544
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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c66
--- Comment #66 from openQA Review openqa-review@suse.de --- 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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c67
--- Comment #67 from openQA Review openqa-review@suse.de --- 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/7753720
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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c68
--- Comment #68 from openQA Review openqa-review@suse.de --- 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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c69
--- Comment #69 from openQA Review openqa-review@suse.de --- 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/7915113
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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c70
--- Comment #70 from openQA Review openqa-review@suse.de --- 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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c71
--- Comment #71 from openQA Review openqa-review@suse.de --- 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/8024697
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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c72
--- Comment #72 from openQA Review openqa-review@suse.de --- 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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c73
--- Comment #73 from openQA Review openqa-review@suse.de --- 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/8220604
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`
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c74
--- Comment #74 from openQA Review openqa-review@suse.de --- 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.
https://bugzilla.suse.com/show_bug.cgi?id=1006815 https://bugzilla.suse.com/show_bug.cgi?id=1006815#c75
--- Comment #75 from openQA Review openqa-review@suse.de --- 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/8790850
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 112 days if nothing changes in this ticket.
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com