Investigate o3 s390x autoyast installation boot failure
For motivation see https://progress.opensuse.org/issues/122059
Autoyast installation for s390x in o3 has been failing while attempting first boot : https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=autoyast_zvm&version=Tumbleweed
There has beem a bug reported, but it is marked as invalid :
The issue cannot be reproduced on x3270, as the setup is different.
The setup for s390x zVM on O3 is different from osd. Some information about o3 workers can be found here: https://progress.opensuse.org/projects/openqav3/wiki/#o3-s390-workers
- Formatting the dasd before installation, results in the system not being able to propose a partitioning.
- Creating an autoyast profile with partitioning included, fails as the system cannot locate the device /dev/disk/by-path/ccw-0.0.0150 . This could indicate that the system cannot connect to lpar after booting, but seems strange because we don't experience the same issue with interactive installation on o3 s390x.
- See draft here: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17063/files
Updated by syrianidou_sofia 4 months ago
- Status changed from New to Resolved
- Assignee set to leli
While working on ticket https://progress.opensuse.org/issues/128693 Lemon has figured out that the xml profile was missing the part where ssh keys should be implemented in the SUT after installation, so that the reconnection with the worker could occur. Now the autoyast zVM test on O3 passes. https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=autoyast_zvm&version=Tumbleweed