Project

General

Profile

Actions

action #128183

closed

coordination #123583: [epic] Agama auto-installation

Automate auto-installation of openSUSE Tumbleweed

Added by JERiveraMoya over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
2023-03-29
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Besides ALP Agama is also capable of installing TW.
The test steps are described here:
https://github.com/openSUSE/agama/blob/master/autoinstallation/README.md
See Epic as reference for previous work

Scope

x86_64 and aarch64 (s390x z/VM I don't think it is achievable a the moment)
This scenario will ONLY check with json.

Acceptance criteria

AC1: Automate the auto-installation of openSUSE Tumbleweed

Additional information

See related work for ALP Bedrock:
https://openqa.opensuse.org/group_overview/96


Files

tw-json.jpg (46.9 KB) tw-json.jpg coolgw, 2023-05-10 02:55

Related issues 1 (0 open1 closed)

Copied to qe-yam - action #128186: Automate auto-installation of openSUSE Leap 16.0Resolvedzoecao2023-03-29

Actions
Actions #1

Updated by JERiveraMoya over 1 year ago

  • Copied to action #128186: Automate auto-installation of openSUSE Leap 16.0 added
Actions #2

Updated by coolgw over 1 year ago

  • Assignee set to coolgw
Actions #3

Updated by coolgw over 1 year ago

  • Status changed from Workable to In Progress
Actions #5

Updated by JERiveraMoya over 1 year ago

depending on answer in https://bugzilla.suse.com/show_bug.cgi?id=1210941 we should consider workaround it, I suspect is the timing, perhaps we need to run the auto-installation via command line once Agama has been launched in order to use json.

Actions #6

Updated by coolgw over 1 year ago

Actions #7

Updated by JERiveraMoya over 1 year ago

coolgw wrote:

I have not seen any answer in https://bugzilla.suse.com/show_bug.cgi?id=1210941.

checking with them in Slack, otherwise we could workaround it.

Actions #8

Updated by coolgw over 1 year ago

Base JERiveraMoya's idea, we try to load system without any extra parameter, and when the default UI start show(means the system bootup ready), then switch to console do agama command step by step, at same time you need check screen from time to time make sure your action is take effect.

I use following commands and the installation job start. One thing need mention root password seems not take effect, but at least this workaround can let system start do installation instead of report dbus error.

set -ex

tmpdir=$(mktemp --directory --suffix "-agama")
echo "working on $tmpdir"

/usr/bin/sleep 30

cat << EOF > ${tmpdir}/profile.json
{
"software": {
"product": "Tumbleweed"
},
"user": {
"fullName": "Jane Doe",
"password": "doe",
"userName": "joe"
},
"root": {
"password": "nots3cr3t"
}
}
EOF

/usr/bin/agama profile validate "${tmpdir}/profile.json" || echo "Validation failed"
/usr/bin/agama config load "${tmpdir}/profile.json"

/usr/bin/agama install
/sbin/reboot

Actions #9

Updated by coolgw over 1 year ago

Attach the UI which after agama load json file, seems root pass setting not take effect.
Then even we start use this workaround implement in Openqa, we will blocked on login session.

Actions #10

Updated by JERiveraMoya over 1 year ago

Remaining part is name new test suite a bit better and isos post the verification so in Agama development we don't see the specific development branch in the jobs.

Actions #11

Updated by coolgw over 1 year ago

Update name in openqa.

Actions #12

Updated by coolgw over 1 year ago

Do some cleanup such as:
-remove all old name results
-update json case to name agama_auto_tumbleweed_bsc1210941
-keep agama_auto_tumbleweed_sh since json's issue still exist, can be used for show other modules result

Actions #13

Updated by coolgw over 1 year ago

  • Description updated (diff)
Actions #14

Updated by JERiveraMoya over 1 year ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF