[y][timeboxed:20h] test fails in await_install
Installation takes too long, resulting in test failure. The issue demonstrates similarity with already fixed bugs:
Possibly related could be the follow up bug which is not resolved yet: https://bugzilla.suse.com/show_bug.cgi?id=1177546
It might be related to load on the network as downloading speed is very low in the failed runs, which might be the case when there are a lot of jobs running. We have triggered https://openqa.suse.de/tests/4854207 , let's see if it works.
openQA test in scenario sle-15-SP3-Online-ppc64le-ssh-X@ppc64le-hmc-single-disk fails in
Always latest result in this scenario: latest
#5 Updated by JERiveraMoya about 1 year ago
- Status changed from In Progress to Feedback
vmstat procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 0 0 0 4686144 113024 2725568 0 0 3 23 21 14 0 0 99 0 0
I cannot find anything relevant from the run openQA: https://openqa.suse.de/tests/4878296 and manually seems to be not reproducible, because is related with ssh installation.
Other heavier installations do not have this problem as they are not done via ssh.
#9 Updated by JERiveraMoya 12 months ago
Logs bumping the timeout: https://openqa.suse.de/tests/4887302/file/logs_from_installation_system-y2logs.tar.bz2
#10 Updated by JERiveraMoya 12 months ago
Installation via ssh is really slow, I cannot even connect to see the first dialog without using -C with ssh forwarding, but even though is terrible slow, so it is reproducible manually. Switching tab to SLE15-SP3 Release Note, the installation is faster, because that screen does not change except for the progress bar.
In summary, the culprit is the forwarding of X over SSH.
#13 Updated by okurz about 2 months ago
This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01
#14 Updated by JERiveraMoya about 2 months ago
- Priority changed from High to Normal
Hi okurz, as described in the bug this ticket is not related with YaST, there is a problem with network speed in the infrastructure for PowerVM. We can see here 52 minutes. We provided all the info needed in the bug (still could be some problem in some package related with ssh). Do you have any suggestion about some other team which could have more insight about this? Thanks.