Project

General

Profile

Actions

action #19140

closed

openqaworker3's workload is too high

Added by nicksinger almost 7 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
2017-05-12
Due date:
% Done:

0%

Estimated time:

Description

Taking a look at
https://openqa.suse.de/tests/930927#step/yast2_snapper/53
and also
https://openqa.suse.de/tests/931099#step/sshd/13

indicates that openqaworker3 has a very high load and the SUTs become unresponsive.
The yast2_snapper issue is also known as bsc#1031864 and bsc#1032831 but this really seems more like an load issue since the postfail_hook on yast2_snapper also times out while logging into the tty to save logs.


Related issues 1 (0 open1 closed)

Related to openQA Project - action #14072: [tools]monitor our loadResolved2016-10-05

Actions
Actions #1

Updated by okurz over 6 years ago

  • Project changed from 46 to openQA Tests
  • Subject changed from [tools] openqaworker3's workload is to high to [tools] openqaworker3's workload is too high
  • Category set to Infrastructure
  • Assignee set to szarate
  • Priority changed from Normal to High

that didn't work. Let's try like this :-)

Actions #2

Updated by szarate over 6 years ago

  • Status changed from New to Feedback
  • Assignee deleted (szarate)

After giving a quick look, doesn't looks like it's happening anymore, or for some reason the load has not been causing failures in the latest builds.

Actions #3

Updated by szarate over 6 years ago

Actions #4

Updated by okurz over 4 years ago

  • Project changed from openQA Tests to openQA Infrastructure
  • Subject changed from [tools] openqaworker3's workload is too high to openqaworker3's workload is too high
  • Category deleted (Infrastructure)
  • Status changed from Feedback to Rejected
  • Assignee set to okurz

yeah I don't think anything has been done but the machine is fine.

Actions

Also available in: Atom PDF