action #116557
closedcoordination #115322: [Epic] Update test coverage based on PRD for migration paths in SLE 15 SP5
HA SLE-15-SP2 LTSS Standalone offline migration + AutoYaST installation
Description
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¶
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_offline_dvd_sle15sp2_ltss_ha_alpha_node01_atmg
- migration_offline_scc_sle15sp2_ltss_ha_alpha_node01_atmg
We will be creating AutoYaST job for standalone installation chained with migration (reusing existing test suite).
It should cover all architectures even ppc64le with PowerVM.
Acceptance criteria¶
AC1: Create new AutoYaST HA textmode image creation in "YaST Maintenance Updates - Development" job group
AC2: Use different name than existing when publishing AutoYaST image and change name of test suite to ha_autoyast_*
AC3: Tackle migration listed in the scope (above) for this ticket and setup as well in 'Migration' job group with name starting with ha_*
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
Notice that we cannot replace yet the test suites in Migration: HA due to we need to still file bugs for new builds for existing configuration (which is replicated for both squad at the moment)
Updated by coolgw about 2 years ago
- Status changed from Workable to In Progress
- Assignee set to coolgw
Updated by JERiveraMoya about 2 years ago
- Description updated (diff)
@coolwg, notice the change about where to setup the migration job and the new name to use.
we could save one step with that.
Updated by zoecao about 2 years ago
- Assignee changed from coolgw to zoecao
Created qcows for sles15sp2 ltss + ha cases:
SLES-15-SP2-aarch64-HA-GM.qcow2
SLES-15-SP2-s390x-HA-GM.qcow2
SLES-15-SP2-x86_64-HA-GM.qcow2
Wei Gao had helped to move them to openqa fixed folder;
Added the sles15sp2 offline ha standalone cases:
ha_migration_offline_dvd_sles15sp2
ha_migration_offline_pscc_sles15sp2
for x86_64, s390x and aarch64;
Add the offline ha standalone cases for power:
ha_migration_offline_dvd_sle15sp2_ltss_pre
ha_migration_offline_dvd_sle15sp2_ltss
ha_migration_offline_pscc_sle15sp2_ltss_pre
ha_migration_offline_pscc_sle15sp2_ltss
VR: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=24.1&groupid=319
MR: https://gitlab.suse.de/coolgw/wegao-test/-/merge_requests/146
Then need to convert the creating qcow image case to AutoYaST.
Updated by JERiveraMoya about 2 years ago
Please, test with branch (using openqa-clone-custom-git-refspec
to create your test matrix) the migration test suites, now the development group is cluttered with many things (MR is fine, just referring how you test it)
For the AutoYaST jobs it is the right place.
Updated by JERiveraMoya about 2 years ago
- Description updated (diff)
Notice change in AC1, that group is triggered everyday by the bot, avoiding for us to have to do it manually.
Also we need some naming convention to distinguish by product what we test, I updated AC2 and AC3.
Updated by JERiveraMoya about 2 years ago
- Subject changed from Adapt existing HA offline standalone migration in dev group with AutoYaST for SLE-15-SP2 to HA SLE-15-SP2 LTSS Standalone offline migration + AutoYaST installation
- Description updated (diff)
Updated by JERiveraMoya about 2 years ago
- Description updated (diff)
Updated in the description your suggestion to cover all the architectures.
Updated by JERiveraMoya about 2 years ago
- Description updated (diff)
Added missed scc test suite to the description.
Updated by zoecao about 2 years ago
JERiveraMoya wrote:
Added missed scc test suite to the description.
I added the cases with 'pscc' (see the [VR here]: the cases which name include ha_ & 15sp2_ltss, for example 'ha_migration_offline_pscc_sles15sp2_ltss')because the migration cases are tested with proxySCC, I think name the cases with 'scc' is not accurate.
Updated by zoecao about 2 years ago
Done with converting installation case to autoyast installation for sles15sp2 ltss:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP2&build=25.1&groupid=251
only done on x86_64, aarch64 and s390x.
VR for the migration cases:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=25.1&groupid=251
Not ready on ppc64le, will work on it.
Updated by zoecao about 2 years ago
Submit PR for the autoyast profiles, and will submit MR for the migration cases to migration daily group after no more problems with the autoyast installation mr.
PR link: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15751
autoyast case MR: https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/406
Updated by zoecao about 2 years ago
I resubmit the MR for the ha standalone migration cases:
https://gitlab.suse.de/coolgw/wegao-test/-/merge_requests/158
Updated by zoecao about 2 years ago
- Status changed from In Progress to Resolved
The MRs and PR are merged, and I checked the test results of ha autoyast installation cases in YaST MUs Dev group, no issues found. So close here.