Project

General

Profile

action #73306

[y][timeboxed:20h] test fails in await_install

Added by syrianidou_sofia about 1 year ago. Updated about 2 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
Target version:
Start date:
2020-10-13
Due date:
% Done:

0%

Estimated time:

Description

Observation

Installation takes too long, resulting in test failure. The issue demonstrates similarity with already fixed bugs:
https://bugzilla.suse.com/show_bug.cgi?id=1177415
https://bugzilla.suse.com/show_bug.cgi?id=1177434

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
await_install

Always latest result in this scenario: latest

during_slow_installation.png (187 KB) during_slow_installation.png JERiveraMoya, 2020-10-23 13:32
before_install.png (184 KB) before_install.png JERiveraMoya, 2020-10-23 13:32
same_scenario_in_s390x.png (331 KB) same_scenario_in_s390x.png JERiveraMoya, 2020-10-26 08:19
10720
10723
10747

History

#1 Updated by riafarov about 1 year ago

  • Subject changed from test fails in await_install to [y] test fails in await_install
  • Target version set to SLE 15 SP3

#2 Updated by riafarov about 1 year ago

  • Subject changed from [y] test fails in await_install to [y][timeboxed:20h] test fails in await_install
  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by JERiveraMoya about 1 year ago

  • Assignee set to JERiveraMoya

#4 Updated by JERiveraMoya about 1 year ago

  • Status changed from Workable to In Progress

#5 Updated by JERiveraMoya about 1 year ago

  • Status changed from In Progress to Feedback

See attachments

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.

#8 Updated by JERiveraMoya about 1 year ago

I noticed how fast in the network (attached screenshot) for s390x, an SSH installation might be a bit slower, because SSH provides encryption throughout the duration of the installation

#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.

#11 Updated by JERiveraMoya 12 months ago

  • Status changed from Feedback to Blocked

#12 Updated by oorlov 3 months ago

  • Target version changed from SLE 15 SP3 to Current

#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.

Also available in: Atom PDF