action #71092
closed
[SLE][Migration][SLE15SP3]test fails in patch_sle: zypper -n rm -t product SLES-LTSS' failed for aarch64 sles12sp3
Added by hjluo over 3 years ago.
Updated over 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
the reason is that in sles12sp3 the ltss was named as 12-SP3-LTSS not SLES-LTSS.
openQA test in scenario sle-15-SP3-Migration-from-SLE12-SPX-to-SLE15-SP3-aarch64-offline_sles12sp3_ltss_media_tcm-wsm_def_full@aarch64 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 21.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Assignee set to tinawang123
- Status changed from New to Rejected
sles12 aarch64 do not support ltss, so we reject this ticket.
- Status changed from Rejected to Workable
- Status changed from Workable to In Progress
- Status changed from In Progress to Blocked
As 12sp3 reg code cannot use now.
- Status changed from Blocked to Rejected
As Marita's mail:
In the PRD of SLES12 SP3 aarch64 is defined as "The scope is limited to partner support" (page 25), so I would suggest to skip the migration of
SLES12 SP3 LTSS -> SLE 15 SP3 for the aarch64 architecture.
It not support this scenario. Close 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: offline_sles12sp3_ltss_media_tcm-wsm_def_full
https://openqa.suse.de/tests/4669109
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"
- The label in the openQA scenario is removed
- Estimated time set to 4.00 h
Also available in: Atom
PDF