Project

General

Profile

Actions
Copy link

action #28267

closed

[sle][functional][svirt-hyperv][sporadic]test fails in install_and_reboot - installation seems to be just very slow and timed out after 5500 seconds, bump timeout on that machine type?

Added by okurz about 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
riafarov
Category:
Bugs in existing tests
Target version:
openQA Project (public) - Milestone 13
Start date:
2017-11-23
Due date:
2018-01-30
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-Installer-DVD-x86_64-minimal+base@svirt-hyperv fails in
install_and_reboot
in the installation. From autoinst-log.txt we can see that the test was aborted after 5500 seconds when the installation was far from done but still ongoing.

Reproducible

Fails since (at least) Build 327.1

Expected result

Last good: Previous job worked so most likely sporadic issue

Problem

I suspect a machine/backend specific performance problem. Suggestion: Just bump timeout on that special slow machine or use TIMEOUT_SCALE.

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by michalnowak about 7 years ago

Pure black screen with X11 pointer in right bottom corner means that xfreerdp disconnected.

The VM installed fine though:

08:44:42.6234 17141 no change: 3975.7s
08:44:43.6245 17141 no change: 3974.7s
[ 2437.555046] reboot: Restarting system

attaching console,wait ...connected!

����08:44:44.6256 17141 no change: 3973.7s
08:44:45.6267 17141 no change: 3972.7s
08:44:46.6277 17141 no change: 3971.7s

We have a xfreerdp-restart functionality but only for load_snapshot where connection gets closed. This could be enhanced.

I updated the translation VM to latest OBS code.

Actions
Copy link
 #2

Updated by okurz about 7 years ago

  • Due date set to 2018-01-30
  • Target version set to Milestone 13

so let's track it until M13 and we can see if that helped.

Actions
Copy link
 #3

Updated by riafarov almost 7 years ago

  • Assignee set to riafarov
Actions
Copy link
 #4

Updated by riafarov almost 7 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #5

Updated by riafarov almost 7 years ago

  • Status changed from In Progress to Resolved

As per Michal's comment, there was not a single failure in install_and_reboot since 348.1, hence resolving. Unfortunately, the run doesn't have a name of the worker which has been used anymore =(

Actions
Copy link

Also available in: Atom PDF