action #116509
Updated by JERiveraMoya over 1 year ago
#### Motivation #### After discussion with SAP and HA squad about the migration update here are the results: https://confluence.suse.com/display/qasle/2022-09-12+SAP+and+HA+migration+update General idea is that QE YaST will own equivalent standalone migrations to the ones that exists for non-standalone (with modification via clusters), consisting on: - AutoYaST installation (selecting the extension and corresponding role and publishing image) - Migration (without any more validation) and SAP/HA squad will connect the standalone system migrated above to its existing procedure: - Boot image that has already modified by cluster - Migration - Validation with clusters In that regard each team will review its own group, and migration with cluster will not start until standalone migration has succeed, making the team independent, but collaborating in case of any potential issue. In theory failures not seen in the standalone migration will be probably caused by cluster modification, so QE SAP/HA will open bugs for that and they will have to figure out what is different. Additional mapping of standalone migration test suite names and cluster migration test suites should provided by our side to make the connection. #### Scope #### In this ticket will will tackle this procedure for the following test suites: - #### Acceptance criteria #### **AC1**: Convert to AutoYaST HA textmode image creation in "Test Development: Migration: SLE15-SP5" job group **AC2**: Find good name for the test suite which allow us to distinguish properly from other dev test suites **AC3**: Tackle migration listed in the scope (above) for this ticket #### Additional information #### PoC by Lemon: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=19.1&groupid=319 - create_hdd_ha_textmode_15SP3 - offline_sles15sp3_pscc_basesys_all_full-standalone-test - create_hdd_ha_textmode_15SP4 - offline_sles15sp4_pscc_basesys_all_full-standalone-test ** draft **