action #108114
closed
[qe-core] test fails in addon_products_sle
Added by zluo over 2 years ago.
Updated about 2 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP3-Online-QR-SLED-x86_64-gnome@uefi fails in
addon_products_sle
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: slindomansilla
The standard scenario where we mainly just follow installation suggestions without any adjustments as long as the default desktop is gnome.
Reproducible¶
Fails since (at least) Build 200.13
Expected result¶
Last good: 200.10 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Start date deleted (
2022-03-10)
- Subject changed from [qa-core] test fails in addon_products_sle to [qe-core] test fails in addon_products_sle
- Status changed from New to Workable
- Parent task set to #107968
New problem in QR.
It seems like a product change that now there is a High Availability license agreement that there wasn't before.
dzedro wrote:
tjyrinki_suse wrote:
New problem in QR.
It seems like a product change that now there is a High Availability license agreement that there wasn't before.
This is happening when the license is different [1] than https://openqa.suse.de/tests/8307161#step/accept_license/3
I guess this should not happen, no idea why is it happening now or why is the license different.
Agree, I also think this should not be happening.
Can we open a bug for this please.
[1] https://github.com/yast/yast-packager/pull/356
@tjyrinki_suse
Cool you guys found this, thanks. How come your are testing HA modules? This is really good, just unexpected.
Thanks for filing the bug too!
@tjyrinki_suse
Cool you guys found this, thanks. How come your are testing HA modules? This is really good, just unexpected.
Not sure why in SLES test we select the HA module too, but indeed it doesn't hurt either.
It this progress issue here still needed as we have the bug to track it?
- Status changed from Workable to Resolved
- Assignee set to tjyrinki_suse
- Priority changed from Normal to High
This ticket in itself is no longer needed, the final conclusion yesterday was that it is a product bug that needs to be fixed, there's nothing to change in the tests.
Also available in: Atom
PDF