action #133547
closed
[qe-core][sle-micro-5.5][aarch64]test fails in disk_boot
Added by rfan1 9 months ago.
Updated 4 months ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-micro-5.5-Default-aarch64-slem_combustion@aarch64 fails in
disk_boot
Test suite description¶
Extended test for combustion provisioning only
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
- Status changed from New to Workable
- Assignee set to zluo
- 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
- Status changed from Rejected to New
- Assignee deleted (
zluo)
- Status changed from New to Feedback
- Assignee set to zluo
Zaoliang, does this happen if you do it on one of your raspberries?
rfan1 wrote in #note-6:
nevertheless the combustion or ignition tests were not really meant to be run outside of x86_64
Why not?
favogt wrote in #note-8:
rfan1 wrote in #note-6:
nevertheless the combustion or ignition tests were not really meant to be run outside of x86_64
Why not?
Probably because it needs some more work than for x86_64, however not impossible. Would be nice to have. Same in ALP.
favogt wrote in #note-8:
rfan1 wrote in #note-6:
nevertheless the combustion or ignition tests were not really meant to be run outside of x86_64
Why not?
Both configs are using a 3rd drive (vdc) to test partitioning and creating a new filesystem (ext4). IIRC, aarch64 could swap the labels thus it can lead to failure as this one
I am ok to closing this ticket and create a new one for the implementation as new test enablement. Should be applicable to all transactional systems that we are testing (MicroOS, SLE Micro and ALP) and possibly to all architectures.
mloviska wrote in #note-10:
favogt wrote in #note-8:
rfan1 wrote in #note-6:
nevertheless the combustion or ignition tests were not really meant to be run outside of x86_64
Why not?
Both configs are using a 3rd drive (vdc) to test partitioning and creating a new filesystem (ext4). IIRC, aarch64 could swap the labels thus it can lead to failure as this one
Which looks like either some QA or product bug (VM host or guest) and that should be investigated.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF