Project

General

Profile

Actions
Copy link

action #129664

closed

coordination #120534: [epic] Provide auto-installation test suites for supporting testing

Create autoyast installation testsuite to publish powerKVM image for sles12sp4 migration tests

Added by leli 11 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Low
Assignee:
syrianidou_sofia
Target version:
Current
Start date:
2023-05-22
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Currently the migration tests for sles12sp5 to sles15sp4 used an outdated image, patch the system and then proceed to installation. As a result, the tests run for a long time and there are a lot of background processes running. Recently an issue occurred where force_scheduled_tasks module would sporadically collide with btrf_cleanup and it would fail due to the load not being settled in time. Additionally, the migration test is very unstable and shows multiple different failures .

Acceptance criteria

AC1: Create powerKVM autoyast installation test suite for sles12sp4 that will publish and updated image in Development job group.
AC2: Link the migration jobs with the new image.

Actions
Copy link
 #1

Updated by JERiveraMoya 11 months ago

  • Status changed from New to Workable
  • Priority changed from Normal to Low
  • Target version set to Current
  • Parent task set to #120534
Actions
Copy link
 #2

Updated by syrianidou_sofia 11 months ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions
Copy link
 #3

Updated by syrianidou_sofia 11 months ago

  • Subject changed from Create autoyast installation testsuite to publish powerKVM image for sles12sp5 migration tests to Create autoyast installation testsuite to publish powerKVM image for sles12sp4 migration tests
  • Description updated (diff)
Actions
Copy link
 #4

Updated by syrianidou_sofia 11 months ago

  • Status changed from In Progress to Resolved

The autoyast installation, under ltss has some issue. Possibly because the repo variables are extended to SP5 instead of SP4, as the parent test is an SP5 installation. https://openqa.suse.de/tests/11211438#step/installation/5
But after noticing that 12SP4 ltss will be out of support in a month, we will not work on this ticket furtherly.

Actions
Copy link
 #5

Updated by openqa_review 11 months ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: offline_sles12sp4_ltss_scc_pcm-contm_def_full@ppc64le
https://openqa.suse.de/tests/11194041#step/first_boot/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
Copy link
 #6

Updated by syrianidou_sofia 11 months ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #7

Updated by openqa_review 10 months ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: offline_sles12sp4_ltss_media_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g
https://openqa.suse.de/tests/11175548#step/force_scheduled_tasks/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
Copy link
 #8

Updated by syrianidou_sofia 10 months ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #9

Updated by openqa_review 9 months ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: offline_sles12sp4_ltss_media_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g
https://openqa.suse.de/tests/11175548#step/force_scheduled_tasks/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
Copy link
 #10

Updated by syrianidou_sofia 9 months ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #11

Updated by openqa_review 9 months ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: offline_sles12sp4_ltss_media_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g
https://openqa.suse.de/tests/11175548#step/force_scheduled_tasks/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
Copy link
 #12

Updated by syrianidou_sofia 9 months ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF