Project

General

Profile

action #124922

coordination #121876: [epic] Handle openQA review failures in Yam squad

Create autoyast installation for SLES-15-SP3-s390x-GM-SDK-gnome-allpatterns.qcow2

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

Status:
In Progress
Priority:
Normal
Assignee:
JRivrain
Target version:
Current
Start date:
2023-02-22
Due date:
% Done:

0%

Estimated time:

Description

Motivation
The case [this one] & [this one] failed to connect registration server for unknown reason, the rmt server is fine, and from the test history, it could connect the server sometimes. I cloned the job with another image, it works fine, so I advise to create up-to-date image for the cases.

ToDo
Create an autoyast installation similar to autoyast_create_hdd_gnome that provides an up-to-date disk image for SLES-15-SP3-s390x-GM-SDK-gnome-allpatterns.qcow2 on a daily schedule.
This auotyast installation can be run in the YaST Maintenance Updates - Development job group (group-ID 446).

Acceptance criteria
AC1: daily image creation by autoyast.
AC2: Migration jobs use the image created by the autoyast.

History

#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: offline_sles15sp3_rmt_basesys-srv-desk-dev-pcm_all_full
https://openqa.suse.de/tests/10555069#step/patch_sle/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.

#2 Updated by openqa_review about 1 month ago

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

This bug is still referenced in a failing openQA test: online_sles15sp3_rmt_basesys-srv-desk-dev_all_full_zypp
https://openqa.suse.de/tests/10957443#step/register_system/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.

#3 Updated by JERiveraMoya 18 days ago

  • Status changed from New to Workable
  • Parent task set to #121876

#4 Updated by JRivrain 16 days ago

  • Status changed from Workable to In Progress
  • Assignee set to JRivrain

#5 Updated by leli 5 days ago

@JRivrain, any update for the ticket? Is there any block issue?

#6 Updated by JRivrain 4 days ago

leli wrote:

@JRivrain, any update for the ticket? Is there any block issue?

Yes, blockers:

  • I spent more time than expected on another ticket with higher priority
  • I could not generate a profile the "standard" way, as I have no vnc access on those s390 workers, and I did not manage to schedule "clone.pm" using INCLUDE_MODULES.

next step to unblock:
Create a yaml schedule, so I will be able to schedule "clone.pm".

#7 Updated by JRivrain 4 days ago

It did not work somehow to schedule auto.pm, I need to create a VM myself on the kvm host,and boot that image from there.

Also available in: Atom PDF