Project

General

Profile

Actions

action #108962

closed

[qe-sap] test fails in ha_cluster_join - connection issue between cluster nodes

Added by lpalovsky over 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
2022-03-25
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-Online-ppc64le-ha_priority_fencing_node02@ppc64le fails in
ha_cluster_join

On HA MM test I am observing temporary connection failures between cluster nodes and probably supportserver.

Cluster node connection issue:
https://openqa.suse.de/tests/8386254#step/ha_cluster_init/15
cluster node qdevice-node01 is trying to reach node03 with: "host -t A qdevice-node03"
It fails first time, but passes on second attempt.
Later while initiating the cluster, node 03 is again not reachable:
https://openqa.suse.de/tests/8386254#step/ha_cluster_init/18

Supportserver connection:
Here a node cannot reach supportserver while connecting iscsi devices
https://openqa.suse.de/tests/8386257#

All issues are observed on ppc64le, but I am seeing one failure on aarch64:

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
https://openqa.suse.de/tests/8376280#step/iscsi_client/13

Reproducible

Fails since (at least) Build 116.4

Expected result

Last good: 113.1 (or more recent)

Actions #1

Updated by lpalovsky over 2 years ago

Actions #2

Updated by maritawerner over 2 years ago

  • Subject changed from test fails in ha_cluster_join - connection issue between cluster nodes to [qe-sap] test fails in ha_cluster_join - connection issue between cluster nodes
Actions #3

Updated by openqa_review over 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: ha_qdevice_node1
https://openqa.suse.de/tests/8662148#step/ha_cluster_init/1

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

Actions #4

Updated by rbranco about 2 years ago

  • Assignee set to lpalovsky
Actions #5

Updated by lpalovsky about 2 years ago

The issue does not appear anymore, therefore the progress ticket can be closed.

Actions #6

Updated by lpalovsky about 2 years ago

  • Status changed from New to Rejected

Closing the ticket since the issue was not observed for months with previous tests being cleaned up by autocleanup.

Actions

Also available in: Atom PDF