Project

General

Profile

Actions

action #170407

open

[qe-core][sle15sp7][xen]test fails in bootloader_svirt, nfsmount `openqa.suse.de:/var/lib/openqa/share/factory/hdd/fixed 6427781120 4264771584 2163009536 67% /var/lib/openqa/share/factory/hdd/fixed` seems gone

Added by rfan1 about 2 months ago. Updated 12 minutes ago.

Status:
Blocked
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Start date:
2024-11-28
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Description

The nfs mount is not there

unreal6:~ # cat /etc/fstab |grep nfs
openqa.suse.de:/var/lib/openqa/share        /var/lib/openqa/share   nfs ro,noauto,nofail,retry=30,x-systemd.mount-timeout=30m,x-systemd.automount,nolock    0 0
unreal6:~ # df |grep /var/lib/openqa/share

I didn't mount it manually, since I think we need to double confirm the automount can be done for each os reboot. we may need to investigate a bit why it is lost.

Observation

openQA test in scenario sle-15-SP7-Online-x86_64-create_hdd_textmode@svirt-xen-hvm fails in
bootloader_svirt

Test suite description

Maintainer: QE Core, asmorodskyi

image creation job used as parent for other jobs testing based on existing installation. Installation in textmode and selecting the textmode "desktop" during installation. Explicitly selecting a bigger disk size as the test relies on snapshots being present which is only the case when the HDD is big enough.

Increased HDDSIZEGB: bsc#1051920

Reproducible

Fails since (at least) Build 42.3

Expected result

Last good: 41.1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure (public) - action #170473: k2.qe.suse.de not reachable from mania:2 size:SResolved2024-11-28

Actions
Actions #1

Updated by dzedro about 2 months ago

Isn't this because of cc-zone ?

unreal6:~ # showmount -e openqa.suse.de
clnt_create: RPC: Timed out
Actions #2

Updated by rfan1 about 2 months ago

dzedro wrote in #note-1:

Isn't this because of cc-zone ?

unreal6:~ # showmount -e openqa.suse.de
clnt_create: RPC: Timed out

Seems that

unreal6:~ # ping 10.145.10.207
PING 10.145.10.207 (10.145.10.207) 56(84) bytes of data.
From 195.135.223.4 icmp_seq=1 Packet filtered
From 195.135.223.4 icmp_seq=2 Packet filtered
Actions #3

Updated by dzedro about 2 months ago

  • Related to action #170473: k2.qe.suse.de not reachable from mania:2 size:S added
Actions #4

Updated by rfan1 about 2 months ago

workaround:

We can use another xen host which is located in zone-cc

  WORKER_CLASS: svirt-xen,openqaw5-xen,zone-cc,region-prg,datacenter-dc7,location-prg2
        VIRSH_HOSTNAME: openqaw5-xen.qe.prg2.suse.org

Actions #6

Updated by vkatkalov about 1 month ago

  • Status changed from New to Feedback

As discussed with @rfan1 adding zone-cc to svirt-xen-hvm machine in OSD helped: https://openqa.suse.de/tests/16142758#

Actions #7

Updated by vkatkalov about 1 month ago

  • Status changed from Feedback to Blocked
Actions #8

Updated by openqa_review 29 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: create_hdd_textmode@svirt-xen-pv
https://openqa.suse.de/tests/16270936#step/bootloader_svirt/1

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 28 days if nothing changes in this ticket.

Actions #9

Updated by rfan1 23 days ago ยท Edited

Currant workaround: for machine svirt-xen-pv/hvm, set WORKER_CLASS=svirt-xen,zone-cc

So currently, we have only one xen server is used: openqaw5

Actions #10

Updated by openqa_review 12 minutes ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: memtest@svirt-xen-hvm
https://openqa.suse.de/tests/16529522#step/bootloader_svirt/1

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 28 days if nothing changes in this ticket.

Actions

Also available in: Atom PDF