action #128081
closed
[security] test fails in bootloader_zkvm in s390x-kvm-sle12-mm variants
Added by tjyrinki_suse about 1 year ago.
Updated 6 months ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-s390x-cc_net_case_server@s390x-kvm-sle12-mm fails in
bootloader_zkvm
Fails since (at least) Build 72.4
Last good: 72.1 (or more recent)
Failing are these tests:
cc_audit_remote_server@s390x-kvm-sle12-mm
cc_audit_remote_client@s390x-kvm-sle12-mm
cc_net_case_server@s390x-kvm-sle12-mm
cc_net_case_client@s390x-kvm-sle12-mm
They used to pass at bootloader_zkvm but fail in boot_to_desktop. Notably though there has been a full pass as well of one of the tests, as shown above.
Most other s390x tests are passing, what is the differentiating thing in these s390x-kvm-sle12-mm using tests that make them fail so early and always? What is the reason, or is there no reason, cc_audit_remote and cc_net_case_server were execute on different configuration that other s390x tests?
- Status changed from New to Workable
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_net_case_client@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/11006453#step/bootloader_zkvm/1
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" or "EOL" (End-of-Life)
- 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.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit_remote_client@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/11063629#step/bootloader_zkvm/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Note https://gitlab.suse.de/qe-security/osd-sle15-security/-/merge_requests/165
That is about s390x-kvm-sle12 -> s390x-kvm, this ticket is about s390x-kvm-sle12-mm.
Interestingly the machine s390x-kvm-sle12-mm has a "machine comment" "This is target for QE security team CC multi-machine tests, 6 VMs can be allocated on it", so it seems it has used to be a specific set of machines for QE Security, and there is no corresponding non-sle12 variant of it. Maybe this ticket could be fixed by simply trying out s390x-kvm? It's not that we wouldn't have other multi machine tests running on s390x without the s390x-kvm-sle12-mm (for example cc_ipsec).
- Status changed from Workable to In Progress
- Assignee set to pstivanin
yep, let's try this. I don't see any difference in the openqa config.
- % Done changed from 0 to 100
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Just recording a note regarding these tests from Richard.
"Yep, we may need to add the bridge br0 on s390x SUT if needed, or we may need to re-write the tests"
Also available in: Atom
PDF