https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-12-18T07:04:42ZopenSUSE Project Management ToolopenQA Tests - action #80532: [qe-asg][HAE] Test fails in cluster_md: unexpected node fencehttps://progress.opensuse.org/issues/80532?journal_id=3588582020-12-18T07:04:42Zokurzokurz@suse.com
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: ha_beta_node02<br>
<a href="https://openqa.suse.de/tests/5179022" class="external">https://openqa.suse.de/tests/5179022</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released"</li>
<li>The label in the openQA scenario is removed</li>
</ol>
openQA Tests - action #80532: [qe-asg][HAE] Test fails in cluster_md: unexpected node fencehttps://progress.opensuse.org/issues/80532?journal_id=3784992021-01-18T10:04:30Zjadamekjulien.adamek@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>I don't know why, but this time, I was able to reproduce the bug on my lab, thanks to this, it was easier to debug.<br>
There was a conflict when the cluster md resource agent was configured whereas the md device was already started in the nodes. I removed the manual start of the md device from the test and after checking the official HA documentation, this is how it should be done.</p>