action #115817
open[qe-sap] pacemaker should be stopped (or not causing an error) for single machine tests
0%
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-ppc64le-migration_online_sle15sp3_ha_alpha_node02@ppc64le fails in
register_system
@Michele Pagot identified several migration jobs in ppc64le where journal messages related to pacemaker are printed on the screen, and make a needle fail to match. Failures look like https://openqa.suse.de/tests/9388278#step/register_system/4 or like https://openqa.suse.de/tests/9387960#step/patch_sle/81. Important bit of information: pacemaker is expected to be failing during the migration jobs, as the cluster is not working at the time. Basically, migration jobs run in single machine mode, and have no way to reach the iSCSI server located in the support server. One thing that we can try is add a module that stops pacemaker during the migration to see if this allows us to not see these messages during the test. What I find interesting is that this seems to be impacting only ppc64le
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 9.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by maritawerner almost 2 years ago
- Subject changed from pacemaker should be stopped (or not causing an error) for single machine tests to [qe-sap] pacemaker should be stopped (or not causing an error) for single machine tests
Updated by openqa_review almost 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_online_sle15sp3_ha_alpha_node02
https://openqa.suse.de/tests/9522020#step/register_system/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_online_sle15sp3_ha_alpha_node02
https://openqa.suse.de/tests/9823779#step/register_system/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 84 days if nothing changes in this ticket.
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.