QA » openQA Project » openQA Tests » qe-yam

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 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_sle15sp2_ltss_ha_alpha_node01_atmg

Acceptance criteria¶

AC1: Use an AutoYaST profile for HA textmode image creation in "YaST Maintenance Updates - Development" job group
AC2: Ensure different image name than existing when publishing AutoYaST image
AC3: Ensure names of image creation test suite and migration start by ha_`
AC4: Enable migration listed in the scope (above) for this ticket 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

Notice that we don't replace yet the test suites in job group 'Migration: HA', once the standalone migration is done, we will delete this job group.