action #19836
closed
[tools]test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
Added by SLindoMansilla almost 7 years ago.
Updated over 4 years ago.
Category:
Regressions/Crashes
Description
Observation¶
openQA test on module yast2_snapper in scenarios
- sle-12-SP3-Server-DVD-ppc64le-allpatterns@ppc64le
- sle-12-SP3-Server-DVD-aarch64-Build0428-allpatterns@aarch64
The test failed to assert serial output, but the verification string can be found on https://openqa.suse.de/tests/999221/file/serial0.txt
It seems like somehow it lose the connection to serial.
Reproducible¶
Fails since Build 0428:
- sle-12-SP3-Server-DVD-ppc64le-allpatterns@ppc64le
- sle-12-SP3-Server-DVD-aarch64-Build0428-allpatterns@aarch64
Expected result¶
Last good:
- sle-12-SP3-Server-DVD-ppc64le-allpatterns@ppc64le
- sle-12-SP3-Server-DVD-aarch64-Build0428-allpatterns@aarch64
Further details¶
Always latest result in these scenarios:
- Subject changed from [sles][functional] test fails in yast2_snapper - failed to assert serial output to [sles][functional] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
- Description updated (diff)
- Has duplicate action #20020: [sle][functional][sporadic] test fails in yast2_snapper due to timed out wait_serial added
- Priority changed from Normal to Urgent
Current issue, failing in tests reproducibly, (slightly) impacting RC validation
- Assignee set to asmorodskyi
- Subject changed from [sles][functional] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64 to [tools] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
- Assignee deleted (
asmorodskyi)
- Closer look into logs showing that issue is happening somewhere in backend so reassign to tools team
- If you are curious why postfail_hook executed twice we already found an answer - because failure_analysis called first time due to soft_failure and later when failure_analysis fails it calls postfail_hook which calls again failure_analysis :). I will fix this right now
- Has duplicate action #19912: soft failed in yast2_snapper not working well added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: om_proxyscc_sled12sp2_allpatterns_full_update_by_yast
http://openqa.suse.de/tests/1057899
- Project changed from openQA Tests to openQA Project
- Subject changed from [tools] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64 to [tools][Sprint 1]] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
- Category changed from Infrastructure to Regressions/Crashes
- Target version set to future
Target version set to future, as this is more about investigating what is happening that fixing it (We know for sure that this can take a while to fix)
- Subject changed from [tools][Sprint 1]] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64 to [tools][Sprint 1] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
- Subject changed from [tools][Sprint 1] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64 to [tools][sprint 201709.1] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
- Subject changed from [tools][sprint 201709.1] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64 to [tools][sprint 201709.2] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
- Subject changed from [tools][sprint 201709.2] test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64 to [tools]test fails in yast2_snapper - failed to assert serial output - ppc64 and aarch64
- Priority changed from Urgent to Normal
- Priority changed from Normal to High
- Priority changed from High to Urgent
- Priority changed from Urgent to Normal
Lowering priority, Seattle 15 is down for now. I will double check through the day and make sure it doesn't comes back later :)
- Related to action #32956: [sle][functional][u][medium] test fails in yast2_snapper - Improve logging added
- Target version changed from future to future
- Related to action #40421: [functional][u][opensuse] test fails in hwsim_wpa2_enterprise_setup for ppc64le added
- Status changed from New to Resolved
- Assignee set to okurz
It seems that with our current worker setup, e.g. openqaworker-arm-1…3, as well as with the ppc64le machines we use we did not encounter this again. Assumed fixed.
Also available in: Atom
PDF