action #116164
closedtest fails in patch_sle - too slow ppc64le workers?
0%
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-ppc64le-migration_offline_scc_sles4sap15sp2@ppc64le-2g fails in
patch_sle
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 19.1
Expected result¶
Last good: 15.2 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by emiura over 1 year ago
- Subject changed from test fails in patch_sle to test fails in patch_sle - too slow ppc64le workers?
Adding further details:
This test was restarted twice already. Each time it is restarted, test fails on a different step.
Updated by maritawerner over 1 year ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
Updated by JERiveraMoya over 1 year ago
- Project changed from qe-yam to openQA Tests
It is using unsupported virtualization, but this ticket remind me that YaST and Migration squad should apply same approach with standalone migration for SAP, in the same way we are doing for HA, due to we need to run installation as a previous step of the migration for PowerVM due it doesn't store snapshots (I will mention this in our next sync call with SAP/HA squad).
I will link the related tickets.
This ticket might remain IMO as the one for deactivate this test suite "for now" for corresponding squad.
Updated by maritawerner over 1 year ago
@JERiveraMoya I have assigned that ticket to the QE yam team and I still think that it makes sende to keep it in the Qe yam's team backlog. There is no other team involved here and I definitely do not want to have it unassigned to any team. Would you be ok to keep it in your backlog till it is cleaned up?
Updated by okurz over 1 year ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
assigning back to "qe-yast" as per #116164#note-5
@JERiveraMoya regarding your comment in #116164#note-3
JERiveraMoya wrote:
It is using unsupported virtualization, but this ticket remind me that YaST and Migration squad should apply same approach with standalone migration for SAP, in the same way we are doing for HA, due to we need to run installation as a previous step of the migration for PowerVM due it doesn't store snapshots (I will mention this in our next sync call with SAP/HA squad).
I will link the related tickets.
This ticket might remain IMO as the one for deactivate this test suite "for now" for corresponding squad.
I agree with you. Maybe you can coordinate that with "qe-sap" how to continue?
Updated by JERiveraMoya over 1 year ago
- Related to coordination #119671: [epic] Improve SAP migrations using auto-installation added
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp2_atmg
https://openqa.suse.de/tests/9871488#step/patch_sle/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.
Updated by JERiveraMoya about 1 year ago
- Status changed from New to Rejected
equivalent job for powervm running without issues in patching as we use directly AutoYaST before migration:
https://openqa.suse.de/tests/10561689