action #112355
Updated by JERiveraMoya almost 2 years ago
#### Motivation #### As we can find the in the summary of this test module: `support_server/meddle_multipaths.pm` the purpose of these two test suites ... draft ... In my understanding is testing installation robootness but I didn't get the following: part related with pxe boot ``` # Summary: A test for the supportserver in the role of (iSCSI) # system disk provider for the SUT. # # During initial installation, while the client is installing its # packages: run a disk access robustness test by meddling with # the LUNs of We need further info about this system disk (the client will see non-fatal # fails of the corresponding multipaths). # # Expected effect: no harm. The client installation feature, where this is supposed # to proceed completely undisturbed (multipath robustness). coming from ``` It looks like Nevertheless it is using a good use of the UI, navigating not only the basic screen, seems suitable for us but some specific ones. It it is not clear that doing AutoYaST installation we could still test the same thing. For both reason too exotic without knowing what is going on if it seems a good candidate to move to YaST Maintenance Updates openqa job group. #### Scope #### All products in maintenance: https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=mru-install-multipath-remote_supportserver&modules=&module_re=&groupid=414&version=&distri=sle&build=20220717-1# #### Acceptance criteria #### **AC1**: Move mru-install-multipath-(remote|remote_supportserver) to YaST MUs fails...