action #178600
closedcoordination #169654: [epic] Create test scenarios for Agama
Add unattended installation for x86_64 which changes language and keyboard in the installed system
0%
Description
We need a default unattended installation with no extras that simply modify the language and keyboard for the installed system, in the similar way that was done in AutoYaST with YaST installer:
https://openqa.suse.de/tests/16990128#
Validation should be minimal, only the login the prompt, given than openQA cannot test in a different language/keyboard in the installed system.
This is the part we changed in AutoYaST:
<language>
<language>cs_CZ</language>
</language>
<keyboard>
<keymap>czech</keymap>
</keyboard>
Check equivalent fields in Agama: https://agama-project.github.io/docs/user/autoyast/reference
Acceptance criteria¶
- AC1: Add unattended installation for single architecture (using jsonnet) which changes language and keyboard in the installed system.
Updated by zoecao about 2 months ago
- Status changed from Workable to In Progress
- Assignee set to zoecao
Updated by zoecao about 2 months ago ยท Edited
I take a manual test with keyboard and language changed to CZ, and generated the jsonnet profile, the format of the language and keyboard is:
localization: {
language: 'cs_CZ.UTF-8',
keyboard: 'cz',
},
Created a PR to add the jsonnet profiles and yaml schedules with the validation of - locale/keymap_or_locale .
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21408
VRs: https://openqa.suse.de/tests/overview?build=chcao_178600&version=16.0&distri=sle
Updated by zoecao about 2 months ago
Asked the developers about [this failure] in the vrs
slack thread: https://suse.slack.com/archives/C02D1T4S58S/p1741772718221869
I filed a bug for it: https://bugzilla.suse.com/show_bug.cgi?id=1239462
BTW, I didn't notice that only need to add testsuite for x86_64, I'll remove the added yaml schedules for ppc64le and s390x in the PR.
Updated by JERiveraMoya about 2 months ago
zoecao wrote in #note-3:
Asked the developers about [this failure] in the vrs
slack thread: https://suse.slack.com/archives/C02D1T4S58S/p1741772718221869
I filed a bug for it: https://bugzilla.suse.com/show_bug.cgi?id=1239462
BTW, I didn't notice that only need to add testsuite for x86_64, I'll remove the added yaml schedules for ppc64le and s390x in the PR.
actually it is not bad approach to try with all in the first try, but there are many test suite that just cannot run in different architectures, it is not for economy of processing :), let's try also aarch64, so only in qemu would make sense. Thanks for the investigation.
Updated by JERiveraMoya about 1 month ago
Ony point missing is to setup the test suite in prod and devel.
Updated by zoecao about 1 month ago
- Status changed from In Progress to Resolved
The testsuites were added to prod and devel groups, resolve here, thanks.