Project

General

Profile

Actions

action #93754

closed

[qe-core][qe-yast][qu] xfs@svirt-xen-pv test fails in setup_libyui on 15-SP2 QU testing

Added by tjyrinki_suse over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2021-06-10
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Full-QR-x86_64-xfs@svirt-xen-pv fails in
setup_libyui

Test suite description

Maintainer: QE Yast, QE Kernel

Installation test with explicit selection of "xfs" instead of default.

Reproducible

Fails since (at least) Build 391.12 (current job)

Expected result

Last good: 391.8 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by tjyrinki_suse over 3 years ago

  • Status changed from New to In Progress
  • Assignee set to tjyrinki_suse
Actions #2

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from xfs@svirt-xen-pv test fails in setup_libyui on 15-SP2 QU testing to [qe-core][qe-yast][qu] xfs@svirt-xen-pv test fails in setup_libyui on 15-SP2 QU testing
Actions #3

Updated by szarate over 3 years ago

  • Target version set to QE-Core: Ready
Actions #4

Updated by oorlov over 3 years ago

The issue seems to be the same as https://bugzilla.suse.com/show_bug.cgi?id=1186072. Previously it was faced on hyperv like here. And the last answer from YaST development team is:

I see nothing yast can do here. You might check with a hyper-v expert on
how to configure hyper-v to leave more memory to the vm.

So, it seems to be configuration issue on hyperv and xen-pv.

Actions #5

Updated by tjyrinki_suse over 3 years ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12684
https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/137

Should be fixed now, maybe I'll wait a bit for possible new builds.

oorlov wrote:

The issue seems to be the same as https://bugzilla.suse.com/show_bug.cgi?id=1186072. Previously it was faced on hyperv like here. And the last answer from YaST development team is:

I see nothing yast can do here. You might check with a hyper-v expert on
how to configure hyper-v to leave more memory to the vm.

So, it seems to be configuration issue on hyperv and xen-pv.

I think you're referring to https://openqa.suse.de/tests/6220593#step/partitioning_raid/85 , right, not the xfs test which was just one of the setup_libyui changes.

Actions #6

Updated by tjyrinki_suse over 3 years ago

  • Status changed from In Progress to Resolved

All merged and in use.

Actions

Also available in: Atom PDF