QA » openQA Project » openQA Tests

Verifying the state of the cluster in the hb_report shows that cluster_md resource failed to start because /etc/md/cluster_md was not present in the system.

Jobs were restarted and taken control of via development mode of openQA to verify the state of cluster_md related resources:

• /etc/md/cluster_md was not present, as reported by journal and hb_report
• Backing iSCSI devices were connected.
• /etc/mdadm.conf was present, and it included in the DEVICE line the paths of 2 iSCSI devices that existed in the system.
• A call to mdadm --assemble --scan failed with retval 2 but no error messages.
• A call to mdadm --assemble --scan --verbose reported that /etc/md/cluster_md RAID could not be initialized because configured UUID was different to the actual UUID.
• Checking with blkid confirmed that the UUID reported by both devices in the MD RAID was different than the one configured in /etc/mdadm.conf

Issue was fixed by:

• Updating the UUID in /etc/mdadm.conf with the one reported by blkid
• Syncing /etc/mdadm/.conf to the other node with csync2
• Cleaning up the cluster_md resource with crm resource cleanup cluster_md

This can be used as the basis for a workaround in the ha/check_after_reboot test module.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15473

PR#15473 merged. Closing this.

The PR introduced some regressions. The following 2 PRs were submitted to fix:

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15479
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15484

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_verify_sle15sp3_ha_alpha_node01_atmg
https://openqa.suse.de/tests/9918670

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

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

This bug is still referenced in a failing openQA test: migration_offline_scc_verify_sle15sp3_ha_alpha_node01
https://openqa.suse.de/tests/11030639

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

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

This bug is still referenced in a failing openQA test: migration_offline_dvd_verify_sle15sp3_ha_alpha_node01
https://openqa.suse.de/tests/13956827

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