QA » openQA Project » openQA Tests » qe-yam

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.

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.

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

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".

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.

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:

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.

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

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.

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

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:

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.

There are no more builds for sp5, closing ?