action #120913
open
[qe-sap] test fails in migrate_clvmd_to_lvmlockd
Added by emiura over 2 years ago.
Updated about 2 months ago.
Category:
Bugs in existing tests
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
- Subject changed from test fails in migrate_clvmd_to_lvmlockd to [qe-sap] test fails in migrate_clvmd_to_lvmlockd
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.
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.
- Priority changed from Normal to Low
This ticket was set to Normal priority but was not updated within the SLO period. The ticket will be set to the next lower priority Low.
Also available in: Atom
PDF