action #117238
Updated by JERiveraMoya about 2 years 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 be provided by our side to make the connection. #### Scope #### [This](https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=patch_sle%2Czypper_patch&module_re=&distri=sle&version=15-SP5&build=21.1&groupid=452#) is is the full list to tackle in the future (notice that we don't have to do it for both nodes, only one, so it is the half of it). But in this ticket will will tackle this procedure only covering what the following existing test suite are covering: - **migration_online_sle15sp4_ha_alpha_node01_atmg** It should be similar to what Lemon did, but using AutoYaST (see additional info). It should cover all architectures except ppc64le. #### Acceptance criteria #### **AC1**: Create new AutoYaST HA textmode image creation in "YaST Maintenance Updates - Development" job group** or reuse it if already exists** group **AC2**: Use a different name than existing when publishing AutoYaST image and change name of test suite for migration `ha_*` **AC3**: Tackle migration listed in the scope (above) for this ticket and setup as well in 'Migration' job group #### Additional information #### Reuse existing AutoYaST profiles created from previous HA tickets for similar purpose. Notice that it is not needed to establish a chained dependency with AutoYaST, just booting the image, due to in the future they will be in different job groups and we don't want to spend the whole time and a new installation before running migration, our goal is only to reduce the time for patching the system. Check similar task in #116509 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 Notice that we don't cannot replace yet the test suites in job group 'Migration: HA', once Migration: HA due to we need to still file bugs for new builds for existing configuration (which is replicated for both squad at the standalone migration is done, we will delete this job group. moment)