action #122173
closedcoordination #120534: [epic] Provide auto-installation test suites for supporting testing
Create auto-installation for Leap 15.4 in Yam Support job group in O3
Added by JERiveraMoya almost 2 years ago. Updated over 1 year ago.
Description
Motivation¶
See #121708 and parent epic
Acceptance criteria¶
AC1: auto-installation (default+gnome) is running in Yam Support job group in O3
AC2: should be able to boot and pass this job https://openqa.opensuse.org/tests/2937470
Updated by JERiveraMoya almost 2 years ago
- Related to action #121708: boot_to_desktop: still attempts to load a 42.1 disk image (and newly fails) added
Updated by JERiveraMoya almost 2 years ago
- Description updated (diff)
- Parent task set to #120534
Updated by leli almost 2 years ago
- Status changed from Workable to In Progress
- Assignee set to leli
Updated by leli almost 2 years ago
Created job for the qcow of leap: https://openqa.opensuse.org/tests/3013797#
VR: https://openqa.opensuse.org/tests/3014272#step/reboot_and_install/9
Updated by leli almost 2 years ago
I will create a new qcow name then replace the qcow in the gnome+import_ssh_keys.
Updated by leli almost 2 years ago
Updated by leli over 1 year ago
leli wrote:
PR submitted: https://github.com/os-autoinst/opensuse-jobgroups/pull/258
After PR merged, I will update test suite gnome+import_ssh_keys to update HDD_1 = opensuse-updated-%VERSION%-%ARCH%-%DESKTOP%-%BUILD%.qcow2 and ORIGIN_SYSTEM_VERSION = 15.4
Updated by JERiveraMoya over 1 year ago
leli wrote:
leli wrote:
PR submitted: https://github.com/os-autoinst/opensuse-jobgroups/pull/258
After PR merged, I will update test suite gnome+import_ssh_keys to update HDD_1 = opensuse-updated-%VERSION%-%ARCH%-%DESKTOP%-%BUILD%.qcow2 and ORIGIN_SYSTEM_VERSION = 15.4
we could do in the same repo, right? but let's wait for the needle creation issue is solved so we are not ping by reviewers and we are certain the job passes.
Updated by leli over 1 year ago
The needle issue is ok now, the verify job pass, https://openqa.opensuse.org/tests/3102576#details
Updated by leli over 1 year ago
PR submitted to update test with new auto-created leap 15.4 qcow, https://github.com/os-autoinst/opensuse-jobgroups/pull/266
Updated by JERiveraMoya over 1 year ago
According to feedback, please address:
- Setup the same image for test suite gnome+do_not_import_ssh_keys as well.
- Use normal 64bit machine
- Perform quick investigation if other medium for the same product version is triggered with less frequency than 5 per day.
Updated by leli over 1 year ago
JERiveraMoya wrote:
According to feedback, please address:
- Setup the same image for test suite gnome+do_not_import_ssh_keys as well.
- Use normal 64bit machine
- Perform quick investigation if other medium for the same product version is triggered with less frequency than 5 per day. The item 1&2 is ok for a new PR. For item 3, if the flavor is not flavor: DVD-Updates, then other job group such as Leap 15.4 Images, they have less frequency than 5 per day, just 1 or 2 per day.
Updated by JERiveraMoya over 1 year ago
leli wrote:
JERiveraMoya wrote:
According to feedback, please address:
- Setup the same image for test suite gnome+do_not_import_ssh_keys as well.
- Use normal 64bit machine
- Perform quick investigation if other medium for the same product version is triggered with less frequency than 5 per day. The item 1&2 is ok for a new PR. For item 3, if the flavor is not flavor: DVD-Updates, then other job group such as Leap 15.4 Images, they have less frequency than 5 per day, just 1 or 2 per day.
then let's move it to another flavor, which one will be? perhaps we could use 'any' flavor but overwrite the iso, at the end what we want is the frecuency, we overwrite with openSUSE-Leap-15.4-DVD-x86_64-Media.iso, make sense?
Updated by leli over 1 year ago
JERiveraMoya wrote:
leli wrote:
JERiveraMoya wrote:
According to feedback, please address:
- Setup the same image for test suite gnome+do_not_import_ssh_keys as well.
- Use normal 64bit machine
- Perform quick investigation if other medium for the same product version is triggered with less frequency than 5 per day. The item 1&2 is ok for a new PR. For item 3, if the flavor is not flavor: DVD-Updates, then other job group such as Leap 15.4 Images, they have less frequency than 5 per day, just 1 or 2 per day.
then let's move it to another flavor, which one will be? perhaps we could use 'any' flavor but overwrite the iso, at the end what we want is the frecuency, we overwrite with openSUSE-Leap-15.4-DVD-x86_64-Media.iso, make sense?
GitHub Actions
/ static-check
Error 400:
Job template name 'gnome+do_not_import_ssh_keys' with opensuse-Tumbleweed-DVD-x86_64 and 64bit is already used in job group 'Development Tumbleweed'
Same issue for 'gnome+import_ssh_keys':
failure on line 1 in job_groups/opensuse_tumbleweed.yaml
GitHub Actions / static-check
Error 400:
Job template name 'gnome+import_ssh_keys' with opensuse-Tumbleweed-DVD-x86_64 and 64bit is already used in job group 'Development Tumbleweed'
So should we remove the test from 'Development Tumbleweed'?
Updated by JERiveraMoya over 1 year ago
leli wrote:
JERiveraMoya wrote:
leli wrote:
JERiveraMoya wrote:
According to feedback, please address:
- Setup the same image for test suite gnome+do_not_import_ssh_keys as well.
- Use normal 64bit machine
- Perform quick investigation if other medium for the same product version is triggered with less frequency than 5 per day. The item 1&2 is ok for a new PR. For item 3, if the flavor is not flavor: DVD-Updates, then other job group such as Leap 15.4 Images, they have less frequency than 5 per day, just 1 or 2 per day.
then let's move it to another flavor, which one will be? perhaps we could use 'any' flavor but overwrite the iso, at the end what we want is the frecuency, we overwrite with openSUSE-Leap-15.4-DVD-x86_64-Media.iso, make sense?
GitHub Actions
/ static-check
Error 400:
Job template name 'gnome+do_not_import_ssh_keys' with opensuse-Tumbleweed-DVD-x86_64 and 64bit is already used in job group 'Development Tumbleweed'So should we remove the test from 'Development Tumbleweed'?
TW run once per day, instead of using some Leap medium, we could use Tumbleweed, so basically the normal flavor for tumbleweed and setup Support images job group with that, then there we overwrite the iso, it will look a bit weird, but we can explain the situation in the job group description.
Regarding the failure, that test suite is supposed to be in the official group failing, we just need to setup with the correct image.
Updated by leli over 1 year ago
Updated by JERiveraMoya over 1 year ago
- Status changed from In Progress to Resolved