action #116533
closedcoordination #115322: [Epic] Update test coverage based on PRD for migration paths in SLE 15 SP5
HA SLE-12-SP4 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_sle12sp4_ltss_ha_alpha_node0{1,2}_atmg
- migration_offline_scc_sle12sp4_ltss_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. (we can aim for ppc64le here which is still PowerKVM)
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 JERiveraMoya about 2 years ago
- Tags deleted (
qe-yast-refinement) - Subject changed from Adapt existing offline standalone migration in dev group with AutoYaST for SLE-12-SP4 to Adapt existing HA offline standalone migration in dev group with AutoYaST for SLE-12-SP4
- Status changed from New to Workable
Updated by leli about 2 years ago
HA is not supported on aarch64 for sles12sp4, so for this ticket, the scope will be on x86_64 and s390x.
Updated by leli about 2 years ago
Now the test already ok on x86_64, https://openqa.nue.suse.com/tests/9627911#; but blocked on s390x https://openqa.nue.suse.com/tests/9627982#step/installation/19 for a bug https://bugzilla.suse.com/show_bug.cgi?id=1203728
Updated by JERiveraMoya about 2 years ago
- Subject changed from Adapt existing HA offline standalone migration in dev group with AutoYaST for SLE-12-SP4 to HA SLE-12-SP4 LTSS Standalone online migration + AutoYaST installation
- 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 HA SLE-12-SP4 LTSS Standalone online migration + AutoYaST installation to HA SLE-12-SP4 LTSS Standalone offline migration + AutoYaST installation
Updated by JERiveraMoya about 2 years ago
- Description updated (diff)
we can aim for ppc64le as well, as it is not PowerVM, just old PowerKVM.
Updated by JERiveraMoya about 2 years ago
- Description updated (diff)
adding missing scc test suite for Online medium to the description.
Updated by leli about 2 years ago
Filed a bug for the autoyast installation of SLES12SP4 on s390x kvm, https://bugzilla.suse.com/show_bug.cgi?id=1204153
Updated by leli about 2 years ago
JERiveraMoya wrote:
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.
Hi, are you sure to put this job of AC1 in "YaST Maintenance Updates - Development" group?
I think we'd better to put the case in "Migration - Development" group and this installation case doesn't need to be run every day. WDYT?
Updated by leli about 2 years ago
The latest test results: https://openqa.nue.suse.com/tests/overview?distri=sle&version=15-SP5&build=25.1&groupid=316
Pass on x86_64 and ppc64le, failed on s390x for bug https://bugzilla.suse.com/show_bug.cgi?id=1204153
Updated by leli about 2 years ago
PR submitted but marked as WIP, https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15673
Updated by leli about 2 years ago
MR created for yast maintenance development group:
https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/401
MR created for migration daily group:
https://gitlab.suse.de/coolgw/wegao-test/-/merge_requests/157
Updated by JRivrain about 2 years ago
- Related to action #116536: HA SLE-12-SP5 Standalone offline migration + AutoYaST installation added
Updated by JERiveraMoya about 2 years ago
looks like we missed to setup AutoYaST for ppc64le to generate the image:
https://openqa.suse.de/tests/overview?distri=sle&version=12-SP4&build=20221030-1&groupid=446
probably the image used remains in your personal dev group, right?
Updated by leli about 2 years ago
JERiveraMoya wrote:
looks like we missed to setup AutoYaST for ppc64le to generate the image:
https://openqa.suse.de/tests/overview?distri=sle&version=12-SP4&build=20221030-1&groupid=446
probably the image used remains in your personal dev group, right?
The test suite already added in the job group https://openqa.suse.de/admin/job_templates/446?, but seems hasn't been triggered, do you know the reason? I guess the OBS hasn't triggered ppc64le for this group.
Updated by JERiveraMoya about 2 years ago
leli wrote:
JERiveraMoya wrote:
looks like we missed to setup AutoYaST for ppc64le to generate the image:
https://openqa.suse.de/tests/overview?distri=sle&version=12-SP4&build=20221030-1&groupid=446
probably the image used remains in your personal dev group, right?The test suite already added in the job group https://openqa.suse.de/admin/job_templates/446?, but seems hasn't been triggered, do you know the reason? I guess the OBS hasn't triggered ppc64le for this group.
Please, try to setup that here: https://gitlab.suse.de/qa-maintenance/metadata/-/blob/master/bot/bot.yml#L405
apparently we also loose it for aarch64, if you have any trouble, please ping me, perhaps that configuration is only related to maintenance updates, and we use it for other purposes, but we are still testing products in maintenance and migrating them, so it should be enough reason for not finding obstacles there, perhaps we could add a comment simply. The medium is setup in https://openqa.suse.de/admin/products if you search for sle.*12.*Server-DVD-Updates.*ppc
.
Consider open a new ticket and work on it directly if you see that it might be some extra work, it is fine for me and this is a bit of a blocker we didn't notice. thanks.