Project

General

Profile

Actions

action #120913

open

[qe-sap] test fails in migrate_clvmd_to_lvmlockd

Added by emiura over 1 year ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-11-24
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Seems like the RE for use_lvmlockd is broken for some reason (worked for me trying locally, could be some migration issue), because afterwards, cluster refuses to start due to lack of this parameter.

Observation

openQA test in scenario sle-15-SP5-Full-x86_64-migration_offline_dvd_verify_sle12sp5_ha_alpha_node01@64bit fails in
migrate_clvmd_to_lvmlockd

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 32.1

Expected result

Last good: 29.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by maritawerner over 1 year ago

  • Subject changed from test fails in migrate_clvmd_to_lvmlockd to [qe-sap] test fails in migrate_clvmd_to_lvmlockd
Actions #2

Updated by acarvajal over 1 year ago

Not sure this is a test issue or an actual bug.

Test passed 5 builds ago (build 29.1) and started failing with build 32.1.

Output for the regular expression in both passing and failing tests are the same:

However, since Build 32.1, the lvmlockd resource cannot be started apparently due to a missing configuration parameter from lvm.conf:

I am cloning and re-running the test to confirm, but in my opinion this is either a bug (which could be related to https://bugzilla.suse.com/show_bug.cgi?id=1204219) or the procedure in order to migrate from clvmd to lvmlockd has changed and the migrate_clvmd_to_lvmlockd test module needs to be updated. Leaving this ticket open in the chance that is the latter rather than the former and commenting both in bsc#1204219 and bsc#1204843 to get more information from the developers.

Actions #3

Updated by slo-gin 4 months 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

Also available in: Atom PDF