action #133541
closed
[qe-core][sle-micro-5.5][s390x-kvm]test fails in firstrun
Added by rfan1 over 1 year ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-micro-5.5-Default-s390x-slem_image_wizard@s390x-kvm-sle12 fails in
firstrun
Test suite description¶
SLE Micro image boot with NO ignition neither combustion disk and default tests. Default tests are transactional-update, rebootmgr, health_check, cockpit service and some other checks specific to SLE Micro.
Reproducible¶
Fails since (at least) Build 7.1_1.3
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Due to the error logs # Test died: Unknown hypervisor: kvm at sle-micro/tests/jeos/firstrun.pm line 75.
We may need to switch the test to s390-zvm setup or we can revise the test code to allow s390-zkvm
- Status changed from New to Workable
all is there to do is to allow kvm when the backend is svirt or allow zvm or kvm when it's s390
- Status changed from Workable to Rejected
Jose Lausuch told me a couple of days ago that condition of starting/scheduling sle-micro-5.5 is not ready yet, so please don't open any ticket for these tests for now. No single test passed through staging, so I won't spend time to investigate why these tests are broken,
- Subject changed from [qe-core][sle-micro-5.5][s390x][zkvm]test fails in firstrun to [qe-core][sle-micro-5.5][s390x-kvm]test fails in firstrun
- Status changed from Rejected to Workable
Zaoliang, the bug is in the test code, and is not related to SCC, but in the firstrun module, verify_hypervisor
all is there to do is to allow kvm when the backend is svirt or allow zvm or kvm when it's s390
Since this week SLE Micro 5.5 builds are official,
working on this issue now.
- Status changed from Workable to Resolved
Also available in: Atom
PDF