action #50138
[microos] test fails in yast2_i: Expects yast2_nfs_client to be in the list
0%
Description
On JeOS, nothing is installed which recommends yast2_nfs_client, so it does not appear in the list of recommended packages.
Observation¶
openQA test in scenario opensuse-15.1-JeOS-for-kvm-and-xen-x86_64-jeos@64bit_virtio-2G fails in
yast2_i
Test suite description¶
Maintainer: fvogt, mnowak
Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64.
Reproducible¶
Fails since (at least) Build 6.12
Expected result¶
Last good: 4.14 (or more recent)
Further details¶
Always latest result in this scenario: latest
History
#1
Updated by SLindoMansilla about 3 years ago
- Subject changed from test fails in yast2_i: Expects yast2_nfs_client to be in the list to [microos] test fails in yast2_i: Expects yast2_nfs_client to be in the list
- Assignee set to mkravec
- Priority changed from Normal to High
It was working here: https://openqa.opensuse.org/tests/833296#step/yast2_i/11
Are you sure it is not a product bug?
mkravec, since you are the maintainer of this test module, could you take a look?
#2
Updated by okurz 9 months ago
- Priority changed from High to Normal
This ticket was set to "High" priority but was not updated within 120 days which is 4 times the period of the SLO for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Normal".
#3
Updated by maritawerner 4 months ago
favogt is this ticket still relevant or can we close it?