action #165204
closedtest fails in ssh_interactive_start
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Azure-BYOS-Hardened-Incidents-x86_64-publiccloud_smoketests_gen1@az_Standard_B2s fails in
ssh_interactive_start
Test suite description¶
Publiccloud smoketests do ensure that the image provides minimal
functionality. The test scenario works as follows.
After the given, pure publiccloud_tools qcow2 image was booted on
an openQA worker, the incident repositories to be tested are
downloaded to it. Then, the public cloud instance is deployed
with the corresponding SLES image, prepared and
registered and the previously downloaded update repositories are
transferred over to that cloud instance. After the system was
patched and rebooted successfully, an interactive SSH session is
created to control the cloud instance and some integral system
information is printed. Finally, it is checked if Systemd was
loaded successfully and if the system can echo a string. In case
the product name contains "Hardened", it is checked if the correct
default Message of the Day (MOTD) for hardened images is set, if
auditd does have rules to always log access or deletion of files
and if at least one account has a password expiration date set.
This scenario is defined by
https://gitlab.suse.de/qac/qac-openqa-yaml
Reproducible¶
Fails since (at least) Build :35140:dtb-armv7l
Expected result¶
Last good: :33620:glibc (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by pdostal 4 months ago
- Status changed from Workable to Resolved
This has been hotfixed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19966