Project

General

Profile

Actions

action #164934

closed

coordination #169657: [epic] Handle test fixes and adjustments

Drop unexpected patterns for migration where all patterns are selected

Added by zoecao 4 months ago. Updated 7 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2024-11-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

For migration test with 'all patterns', we need exclude some patterns not in the white list, ex: fips,wsl etc.
On powerVM, migration test use chained jobs so need make sure to exclude these patterns in both jobs.

Suggest to change the installation test to Autoyast and exclude these unexpected patterns ex: fips, wsl etc. from AY profile.

Acceptance criteria

AC1: Change the installation (pre migration) test to Autoyast and exclude these unexpected patterns ex: fips, wsl etc. from AY profile.

Additional information

List of scenarios failing:
https://openqa.suse.de/tests/overview?result=failed&result=incomplete&result=timeout_exceeded&arch=&flavor=&machine=&test=&modules=select_patterns&module_re=&group_glob=¬_group_glob=&comment=&distri=sle&version=15-SP7&build=39.2&groupid=265#


Related issues 1 (1 open0 closed)

Related to qe-yam - action #169789: Change powerVM migration pre cases to use autoyast and exclude fips,wsl patternIn Progresshjluo2024-11-13

Actions
Actions #1

Updated by openqa_review 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migr_sles15sp4_live-basesys-srv-desktop-dev-contm-lgm-tsm-wsm-pcm_all_extras
https://openqa.suse.de/tests/15263591#step/yast2_migration/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #2

Updated by openqa_review 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migr_sles15sp4_all_pre
https://openqa.suse.de/tests/15354618#step/select_patterns/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #3

Updated by openqa_review about 2 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migr_sles15sp4_all_pre
https://openqa.suse.de/tests/15613858#step/select_patterns/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

Actions #4

Updated by JERiveraMoya 26 days ago

  • Tags set to qe-yam-nov-sprint
  • Subject changed from To review the patterns lists for migration testings of all patterns scenarios to Drop necessary patterns for migration where all patterns are selected
  • Description updated (diff)
  • Status changed from New to Workable
  • Parent task set to #151816

I'm not sure anyone has all the overview to answer the questions you have in this ticket, I think the problem is to have designed years ago migrations with all patterns, but we are many years late to have agreed some sort of set of migration with system role scenarios + some extended ones (to cover additional packages) with Release Managers.

I would focus on this ticket on fix the scenarios failing.

I will put on workable only with this goal. If you think there is something else to do, you can create another ticket, but labeling with this general ticket scenarios in production is not going to be straightforward, so with my suggestion the scope should be more reasonable.

Actions #5

Updated by JERiveraMoya 26 days ago

  • Description updated (diff)
Actions #6

Updated by hjluo 26 days ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #7

Updated by hjluo 26 days ago · Edited

  • In Build36.1 these cases are affected:
    • migr_sles15sp4_all_pre@ppc64le-spvm
    • migr_sles15sp4_desktop-dev_all_pre
    • migr_sles15sp4_desktop-python3_all_pre
    • migr_sles_continuous_15sp4_15sp5_ph0

In Build39.2 these are:

Actions #8

Updated by hjluo 25 days ago

  • After discuss with @leli, we'd try first select all patterns then unselect fips then click OK to avoid the conflicts. ans still trying.
Actions #9

Updated by hjluo 22 days ago

Actions #10

Updated by JERiveraMoya 22 days ago

  • Parent task changed from #151816 to #169657
Actions #11

Updated by leli 21 days ago

  • Subject changed from Drop necessary patterns for migration where all patterns are selected to Drop unexpected patterns for migration where all patterns are selected
  • Description updated (diff)
Actions #12

Updated by hjluo 21 days ago

Now after many tries we'd like back to autoyast to save UI time.

Actions #13

Updated by hjluo 20 days ago · Edited

Loading repository data...
Reading installed packages...
S | Name | Version | Repository | Dependency
---+----------------+-------------------------+--------------------------------------------+-----------
v | 32bit | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | 32bit | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |
v | apparmor | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | apparmor | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |
v | base | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | base | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |
v | documentation | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | documentation | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |
v | enhanced_base | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | enhanced_base | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |
v | fips | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | fips | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |
v | fips | 20171206-12.3.1 | SLE-Module-Server-Applications15-SP4-Pool |
X | fips-certified | 20200124-150400.20.10.1 | SLE-Product-SLES15-SP4-LTSS-Updates |
v | fonts | 20190130-1.15 | SLE-Module-Basesystem15-SP4-Pool |
v | gnome_basic | 20201210-150400.5.3 | SLE-Module-Desktop-Applications15-SP4-Pool |
v | sap_server | 20171206-12.6.1 | SLE-Module-Server-Applications15-SP4-Pool |
v | sw_management | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | sw_management | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |
v | wsl_base | 20221221-150400.3.8.1 | SLE-Module-Basesystem15-SP4-Updates |
v | wsl_base | 20221020-150400.3.5.1 | SLE-Module-Basesystem15-SP4-Updates |
v | wsl_gui | 20221221-150400.3.8.1 | SLE-Module-Basesystem15-SP4-Updates |
v | wsl_gui | 20221020-150400.3.5.1 | SLE-Module-Basesystem15-SP4-Updates |
v | wsl_systemd | 20221221-150400.3.8.1 | SLE-Module-Basesystem15-SP4-Updates |
v | wsl_systemd | 20221020-150400.3.5.1 | SLE-Module-Basesystem15-SP4-Updates |
v | x11 | 20200124-150400.20.4.1 | SLE-Module-Basesystem15-SP4-Updates |
v | x11 | 20200124-150400.18.4 | SLE-Module-Basesystem15-SP4-Pool |

Actions #15

Updated by hjluo 20 days ago

  • Subtask #169789 added
Actions #16

Updated by JERiveraMoya 20 days ago

  • Subtask deleted (#169789)
Actions #17

Updated by JERiveraMoya 20 days ago

  • Related to action #169789: Change powerVM migration pre cases to use autoyast and exclude fips,wsl pattern added
Actions #18

Updated by hjluo 20 days ago · Edited

  • MR for 15sp5 PowerVM all pattern conflict.
Actions #19

Updated by hjluo 19 days ago · Edited

  • PR_20629 to remove wsl and fips in zypper_patch and patch_sle for migration to sle-15-SP7.
  • After discussion with Lemon, we'd try BREAK_DEP=1 to workaround it.and it can't boot up.
Actions #21

Updated by hjluo 18 days ago

  • PR and MR were merged and now regtrigger all failed cases.
Actions #22

Updated by hjluo 14 days ago · Edited

  • MR to remove CC and wsl from 15sp4 all patterns in Milestone.
Actions #24

Updated by hjluo 7 days ago

  • Status changed from In Progress to Resolved
  • All migration cases in build 41.1 and all Milestone cases in 40.1 were verified. close this ticket as resolved.
Actions

Also available in: Atom PDF