Project

General

Profile

Actions

action #116536

closed

coordination #115322: [Epic] Update test coverage based on PRD for migration paths in SLE 15 SP5

HA SLE-12-SP5 Standalone offline migration + AutoYaST installation

Added by JERiveraMoya about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-09-14
Due date:
% Done:

0%

Estimated time:

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_sle12sp5_ha_alpha_node0{1,2}_atmg
  • migration_offline_scc_sle12sp5_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)


Files

bug.png (70 KB) bug.png JRivrain, 2022-10-08 18:28

Related issues 1 (0 open1 closed)

Related to qe-yam - action #116533: HA SLE-12-SP4 LTSS Standalone offline migration + AutoYaST installationResolvedleli2022-09-14

Actions
Actions #1

Updated by coolgw about 2 years ago

Q:create_hdd_ha_textmode_15SP3 will run one time or every time openqa trigger?

Actions #2

Updated by JERiveraMoya about 2 years ago

  • Subject changed from Adapt existing offline standalone migration in dev group with AutoYaST for SLE-12-SP5 to Adapt existing HA offline standalone migration in dev group with AutoYaST for SLE-12-SP5
Actions #3

Updated by JERiveraMoya about 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #4

Updated by JERiveraMoya about 2 years ago

  • Description updated (diff)
Actions #5

Updated by JRivrain about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JRivrain
Actions #6

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.

Actions #7

Updated by JERiveraMoya about 2 years ago

  • Subject changed from Adapt existing HA offline standalone migration in dev group with AutoYaST for SLE-12-SP5 to HA SLE-12-SP5 Standalone offline migration + AutoYaST installation
  • Description updated (diff)
Actions #8

Updated by JERiveraMoya about 2 years ago

  • Description updated (diff)
Actions #9

Updated by JERiveraMoya about 2 years ago

  • Description updated (diff)

adding missing scc test suite for Online medium to the description.

Actions #10

Updated by JRivrain about 2 years ago

Hitting a bug with cloned profiles, see attachment, but it works with profile adapted (simplified) from create_hdd_maintenance. Regarding the bug I guess we should report it.

PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15665
MR https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/400

For now, only create_hdd on x86_64.
The cloned profiles based on migration_offline_scc_sle12sp5_ha_alpha_node01_atmg included more config and some extra packages and patterns, we could discuss if we want these.

Actions #11

Updated by JRivrain about 2 years ago

  • Related to action #116533: HA SLE-12-SP4 LTSS Standalone offline migration + AutoYaST installation added
Actions #13

Updated by JRivrain about 2 years ago

In previous discussions, I understood that we wanted to create a separate test suite for migration, also with autoyast. That would look like:
parent job: ha_autoyast_create_hdd_textmode_12sp4 --> child job: ha_autoyast_migrate_sle12spX_to_sle12_sp5.
But then, I see that in https://progress.opensuse.org/issues/116533 and https://progress.opensuse.org/issues/116557, it was chained instead to offline_sles15sp3_pscc_basesys_all_full-standalone-test or other existing tests, and tickets were closed.
Should I do the same ?
If so, it works to directly to chain it with migration_offline_dvd_sle12sp4_ltss_ha_alpha_node01_atmg, that would be more straightforward.
I don't really know what to do next.

Actions #14

Updated by JERiveraMoya about 2 years ago

Let's discuss it in next daily, there is no chained dep between ay creational test suite and migration job.
btw, we need for sle 12 sp4 and sle 12 sp5 ppc64le with PowerKVM enable as well, did you cover that? (for sle 15 we don't need it because that virtualization is not supported and when doing PowerKVM the AutoYaST job is directly in Migration job group not in development).

Actions #16

Updated by JRivrain about 2 years ago

  • Status changed from In Progress to Resolved

All merged and working

Actions

Also available in: Atom PDF