action #88335
closedSUT loose Ethernet connection randomly
0%
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).
- Ethernet was working at
networkingtest step: https://openqa.opensuse.org/tests/1609119#step/networking/11 - But fails at https://openqa.opensuse.org/tests/1609119#step/transactional_update/43 and confirmed on log uploads attempt: https://openqa.opensuse.org/tests/1609119/modules/transactional_update/steps/108
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
Updated by ggardet_arm almost 4 years ago
- Related to action #87797: [opensuse][jeos] DNS record lost on SUT added
Updated by ggardet_arm almost 4 years ago
- Related to action #88337: [qac][microos][sporadic] test fails in networking added
Updated by okurz almost 4 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:
- 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"
- The label in the openQA scenario is removed
Updated by tjyrinki_suse over 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)
Updated by tjyrinki_suse over 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.