Project

General

Profile

Actions
Copy link

action #50138

open

[microos] test fails in yast2_i: Expects yast2_nfs_client to be in the list

Added by favogt about 5 years ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
mkravec
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-04-08
Due date:
% Done:

0%

Estimated time:
Difficulty:

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

Actions
Copy link
 #1

Updated by SLindoMansilla about 5 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?

Actions
Copy link
 #2

Updated by okurz over 2 years 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".

Actions
Copy link
 #3

Updated by maritawerner over 2 years ago

@favogt is this ticket still relevant or can we close it?

Actions
Copy link
 #4

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #5

Updated by slo-gin about 1 month ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link

Also available in: Atom PDF