action #120142
Updated by JERiveraMoya about 2 years ago
#### ## Observation openQA test in scenario sle-15-SP5-Online-s390x-create_hdd_autoyast_containers@s390x-kvm-sle12 fails in [console](https://openqa.suse.de/tests/9304820/modules/console/steps/2) trying to connect to a s390x kvm instance over ssh but the system is not reachable (yet), likely the connection attempt only tries for up to certain value. For s390x-kvm-sle12 seems that 60 seconds default 30s which is not enough. We should as minimum increase enough for all cases it seems. ## Reproducible Fails since (at least) Build [9.1](https://openqa.suse.de/tests/9301501) https://openqa.suse.de/tests/9304820#next_previous shows 7/12 test failing with the timeout in lib/susedistribution.pm when connecting ssh in `activate_console` same error so pretty reproducible. ## Expected result #### Acceptance criteria **AC1**: Increase timeout Last good: (unknown) (or more recent). It is not clear if this was ever stable for ssh connection autoyast based installations on s390x kvm. ## Further details #### Additional information Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online&machine=s390x-kvm-sle12&test=create_hdd_autoyast_containers&version=15-SP5) Consider to apply some logic applied by other backends some "reachiability" checks, e.g. calling first ping, then nc on port 22 before trying to select a console.