Project

General

Profile

Actions
Copy link

action #91791

closed

[CI]worker1.qa1.suse.asia our of memory issue

Added by JNa over 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
okurz
Category:
Regressions/Crashes
Target version:
QA (public) - future
Start date:
2021-04-27
Due date:
% Done:

0%

Estimated time:

Description

Background:during local openQA testing,found worker1.qa1.suse.asia can
not allocate memory

worker1:~ # free -h
total used free shared buff/cache available
Mem: 31Gi 29Gi 886Mi 11Mi 1.0Gi 1.3Gi
Swap: 4.0Gi 2.5Gi 1.5Gi

worker around:
restart some openqa worker service

Actions
Copy link
 #1

Updated by JNa over 3 years ago

  • Status changed from New to Workable
Actions
Copy link
 #2

Updated by cachen over 3 years ago

It looks like local openQA may need a new machine for worker.
I will take this as a budget requirement to FY22.

Actions
Copy link
 #3

Updated by JNa over 3 years ago

During GMC testing,there are 12 jobs are running same time, the worker1 memory status is:

worker1:~ # free -h
total used free shared buff/cache available
Mem: 31Gi 18Gi 10Gi 11Mi 1.9Gi 12Gi
Swap: 4.0Gi 3.2Gi 828Mi

Actions
Copy link
 #4

Updated by zyuhu over 3 years ago

Add necessary background information, then raise this issue to qe-tools team.

Actions
Copy link
 #5

Updated by JNa over 3 years ago

during HANA performance testing,we found ,a continuous and long time running(2 weeks) on local openqa ,cause worker machine memory leak,after reboot worker,issue fixed.

Actions
Copy link
 #6

Updated by zyuhu over 3 years ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #7

Updated by zyuhu over 3 years ago

  • Assignee changed from JNa to zyuhu
Actions
Copy link
 #9

Updated by okurz over 3 years ago

  • Project changed from 205 to openQA Project (public)
  • Category set to Regressions/Crashes
  • Priority changed from Normal to Low
  • Target version set to future

as @zyuhu made me aware of the ticket I will move it to the openQA issue tracker

@zyuhu or others please add relevant information, e.g. "steps to reproduce".

Actions
Copy link
 #10

Updated by okurz over 2 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from zyuhu to okurz

no response, I assume the problem was solved with a hardware replacement.

Actions
Copy link

Also available in: Atom PDF