QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16941

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.

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

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.

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

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.

Update name in openqa.

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