Project

General

Profile

Actions

action #88335

closed

SUT loose Ethernet connection randomly

Added by ggardet_arm about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario microos-Tumbleweed-MicroOS-Image-Kubic-kubeadm-aarch64-kubeadm@aarch64_lse_smp4 fails in
transactional_update

SUT loose Ethernet connection randomly on ip-10-0-0-58 worker (AWS M6g running SLE15-SP2).

Test suite description

Reproducible

Fails since (at least) Build 20210118

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (1 open0 closed)

Related to openQA Tests - action #88337: [qac][microos][sporadic] test fails in networkingNew

Actions
Actions #2

Updated by ggardet_arm about 3 years ago

  • Related to action #88337: [qac][microos][sporadic] test fails in networking added
Actions #3

Updated by okurz about 3 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: kubeadm@
https://openqa.opensuse.org/tests/1625789

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"
  3. The label in the openQA scenario is removed
Actions #4

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from SUT loose Ethernet connection randomly to [qac][microos] SUT loose Ethernet connection randomly
  • Start date deleted (2021-01-29)
Actions #5

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from [qac][microos] SUT loose Ethernet connection randomly to SUT loose Ethernet connection randomly
  • Status changed from New to Resolved

The transactional update is not now seen in the recent history of job runs. Maybe the 88337 with the [sproradic] tag could be kept open however if it's the same root problem.

Actions

Also available in: Atom PDF