action #87973
Updated by riafarov over 3 years ago
## Observation
This is known flow, that in order not to get affected by other installations, as well as not to accidentally affect other installations, when registering/de-registering new modules, we should generate new suse connect credentials, which can be easily done by cleaning them up and conducting registration.
We already do so in tests/installation/addon_products_via_SCC_yast2.pm
s390x failure is used as an example, but we have same flow in qemu and were just lucky for now.
`lib/registration.pm` contains required methods. We need to call cleanup_registration and then register needed modules.
openQA test in scenario sle-15-SP3-Online-s390x-yast2_gui@s390x-kvm-sle12 fails in
[setup_libyui_running_system](https://openqa.suse.de/tests/5304793/modules/setup_libyui_running_system/steps/7)
## Test suite description
Maintainer: zluo, riafarov
Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.
## Reproducible
Fails since (at least) Build [127.1](https://openqa.suse.de/tests/5304793) (current job)
## Expected result
Last good: [124.5](https://openqa.suse.de/tests/5286546) (or more recent)
## Further details
Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online&machine=s390x-kvm-sle12&test=yast2_gui&version=15-SP3)