QA » openQA Project » openQA Tests » qe-yam

Motivation¶

Solve sporadic failures like this one when using SUSEConnect command line tool.
Instead of implementing a retry for each single command like it has been done in other places specifically for registration, we should focus in YaST scope for testing and stop using the command line tool and extend testing a bit with the YaST module.

Scope¶

All products in maintenance:
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=yast2_registration&module_re=&distri=sle&build=20220607-1&groupid=421#

Acceptance criteria¶

AC1: Use only YaST module yast2 registration to re-register the system and verification of the registration.
AC2: Unschedule next test module console/suseconnect

Suggestions¶

Instead of using the command line tool to clean up the registration at the beginning, we can use the option of the YaST Module 'Register again'.
As you could notice, switching off networking in an installed system and calling yast2 registration troughs an error, which mean that internally is connecting to the server in similar way that the command line tool would do. Therefore the final verification of the current installed product modules can also be done reopening the yast module again.
Discard libyui REST for now as the goal is just stabilize and probably this would require no much code and a couple of needles (one at the beginning, one at the end) per each product, in other words, it should be cheap to do it in theory.