action #124922
closedcoordination #130072: [epic] Handle openQA adaptions in Yam squad - SLE 15 SP6
Create autoyast installation for SLES-15-SP3-s390x-GM-SDK-gnome-allpatterns.qcow2
Added by zoecao about 1 year ago. Updated 5 months ago.
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.
Updated by openqa_review about 1 year 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by openqa_review about 1 year 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by JERiveraMoya 12 months ago
- Status changed from New to Workable
- Parent task set to #121876
Updated by JRivrain 11 months 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".
Updated by openqa_review 11 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/11194074#step/patch_sle/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by JERiveraMoya 11 months ago
- Parent task changed from #121876 to #130072
Updated by leli 11 months ago
JRivrain wrote:
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".
I think we can clone a job for create_hdd in functional job group to create the qcow on normal way while not through autoyast, then clone_system from that new job. WDYT?
Example to create qcow:
/usr/share/openqa/script/clone_job.pl --within-instance http://openqa.nue.suse.com xxxxxx --apikey xxx --apisecret xxx _GROUP=0 TEST=create_hdd_SLES-15-s390x-GM-allpatterns.qcow2 PUBLISH_HDD_1=SLES-15-s390x-GM-allpatterns.qcow2 REPO_0=SLE-15-Installer-DVD-s390x-GM-DVD1 SCC_DEREGISTER=1 SCC_URL=https://scc.suse.com BETA=0 VERSION=15 _GROUP=0 HDDSIZEGB=100 PATTERNS=all SCC_REGCODE=xxx EXCLUDE_MODULES=no_separate_home
Updated by JRivrain 11 months ago
leli wrote:
JRivrain wrote:
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".I think we can clone a job for create_hdd in functional job group to create the qcow on normal way while not through autoyast, then clone_system from that new job. WDYT?
Example to create qcow:
/usr/share/openqa/script/clone_job.pl --within-instance http://openqa.nue.suse.com xxxxxx --apikey xxx --apisecret xxx _GROUP=0 TEST=create_hdd_SLES-15-s390x-GM-allpatterns.qcow2 PUBLISH_HDD_1=SLES-15-s390x-GM-allpatterns.qcow2 REPO_0=SLE-15-Installer-DVD-s390x-GM-DVD1 SCC_DEREGISTER=1 SCC_URL=https://scc.suse.com BETA=0 VERSION=15 _GROUP=0 HDDSIZEGB=100 PATTERNS=all SCC_REGCODE=xxx EXCLUDE_MODULES=no_separate_home
Sorry this comment was outdated, the qcow has been generated long ago, now we have this problem that we already discussed https://openqa.suse.de/tests/11278281. I tried the workarounds that we have been talking about but none works.
Updated by JRivrain 11 months ago
Sorry for delays, I had problems with the workaround, then with the worker, so I had to try different things, and also started working on other things in parallel.
PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17148
Updated by openqa_review 10 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/11194074#step/patch_sle/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by JERiveraMoya 10 months ago
- Status changed from In Progress to Resolved
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_sles15sp3_rmt_basesys-srv-desk-dev-pcm_all_full
https://openqa.suse.de/tests/11194074#step/patch_sle/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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_sles15sp3_rmt_basesys-srv-desk-dev-pcm_all_full
https://openqa.suse.de/tests/11194074#step/patch_sle/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by openqa_review 5 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_sles15sp3_rmt_basesys-srv-desk-dev-pcm_all_full
https://openqa.suse.de/tests/11194074#step/patch_sle/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 136 days if nothing changes in this ticket.