Project

General

Profile

Actions

action #117238

closed

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

HA SLE-15-SP4 Standalone online migration + AutoYaST installation

Added by JERiveraMoya over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
2022-09-26
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 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_sle15sp4_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.

Actions #1

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #2

Updated by JERiveraMoya over 1 year ago

  • Priority changed from Normal to High
Actions #3

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #4

Updated by JERiveraMoya over 1 year ago

  • Subject changed from Adapt existing HA online standalone migration in dev group with AutoYaST for SLE-15-SP4 to HA SLE-15-SP4 Standalone online migration + AutoYaST installation
Actions #5

Updated by zoecao over 1 year ago

Checking this ticket, the AC1 & AC2 in this ticket have been covered by [ticket's] AC1 & AC2. For the same migration path (from 15SP4 to 15SP5), the offline migration method cases and online migration method cases use the same image.

Actions #6

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #7

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #8

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #9

Updated by JERiveraMoya over 1 year ago

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

Updated by jgwang over 1 year ago

  • Assignee set to jgwang
Actions #11

Updated by shukui over 1 year ago

  • Status changed from Workable to In Progress
Actions #12

Updated by zoecao over 1 year ago

Hi Wangjun, for this 15sp4 ha online case, no need to create autoyast installation any longer, I have done it, see cases:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=25.1&groupid=251
And you need to add one online case for each arch (x86_64,s390x,aarch64):
ha_migration_online_pscc_sles15sp4
For ppc64le, need to use PowerVM, so need to add two cases for this ticket:
ha_migration_online_pscc_sle15sp4_pre, ha_migration_online_pscc_sle15sp4
You can reference the power cases here:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=25.1&groupid=251
And you can add your cases to this group, when they are ready, need to submit MR and add the case to Migration group.
If any questions, feel free to contact me.

Actions #13

Updated by jgwang over 1 year ago

zoecao wrote:

Hi Wangjun, for this 15sp4 ha online case, no need to create autoyast installation any longer, I have done it, see cases:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=25.1&groupid=251
And you need to add one online case for each arch (x86_64,s390x,aarch64):
ha_migration_online_pscc_sles15sp4
For ppc64le, need to use PowerVM, so need to add two cases for this ticket:
ha_migration_online_pscc_sle15sp4_pre, ha_migration_online_pscc_sle15sp4
You can reference the power cases here:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=25.1&groupid=251
And you can add your cases to this group, when they are ready, need to submit MR and add the case to Migration group.
If any questions, feel free to contact me.

Thank you very much, I will have a try.

Actions #14

Updated by jgwang over 1 year ago

I have created a preview version of "ha_migration_online_pscc_sles15sp4" case here:

could you help to review and give me some suggestions ?

Actions #15

Updated by zoecao over 1 year ago

Hi Wangjun,

Some suggestions for you:

  • The cases of x86_64, s390x and aarch64 arches are good. Just one tip for you that the published qcow name is changed to 'autoyast-SLES-15-SP4-%ARCH%-HA-updated.qcow2', so if you need to rerun your jobs, I advise you to change the setting of HDD_1 to 'autoyast-SLES-15-SP4-%ARCH%-HA-updated.qcow2' in cases of you have to re-run the installation job in the before. If you don't need to re-run your jobs, change the HDD_1 setting when you submit MR would be fine.
  • For the ppc64le case, you need to use autoyast installation for the "pre" case, please refer to the offline ppc64le cases here: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=25.1&groupid=251

jgwang wrote:

I have created a preview version of "ha_migration_online_pscc_sles15sp4" case here:

could you help to review and give me some suggestions ?

Actions #16

Updated by jgwang over 1 year ago

zoecao wrote:

Hi Wangjun,

Some suggestions for you:

  • The cases of x86_64, s390x and aarch64 arches are good. Just one tip for you that the published qcow name is changed to 'autoyast-SLES-15-SP4-%ARCH%-HA-updated.qcow2', so if you need to rerun your jobs, I advise you to change the setting of HDD_1 to 'autoyast-SLES-15-SP4-%ARCH%-HA-updated.qcow2' in cases of you have to re-run the installation job in the before. If you don't need to re-run your jobs, change the HDD_1 setting when you submit MR would be fine.
  • For the ppc64le case, you need to use autoyast installation for the "pre" case, please refer to the offline ppc64le cases here: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=25.1&groupid=251

thank you, good suggestions, I will improve the cases.

Actions #17

Updated by jgwang over 1 year ago

after improving the cases, these cases passed:

but the case for ppc64le doesn't pass and I am debugging it.

Actions #18

Updated by jgwang over 1 year ago

I created PR/MR to finish this ticket:

please help to review them

Actions #19

Updated by coolgw over 1 year ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF