Project

General

Profile

Actions
Copy link

action #77209

closed

workers on o3 machine rebel provide no "WORKER_HOSTNAME" value anymore but it shows up in journal of worker service

Added by okurz over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
SLindoMansilla
Category:
-
Target version:
openQA Project - Ready
Start date:
2020-11-09
Due date:
% Done:

0%

Estimated time:

Description

Observation

For example https://openqa.opensuse.org/admin/workers/384 shows an empty field for "WORKER_HOSTNAME".

Last good: https://openqa.opensuse.org/tests/1464503 from 2020-11-08 22:56Z
First bad: https://openqa.opensuse.org/tests/1464540 from 2020-11-09 04:40Z

what looks certainly related is that
https://github.com/os-autoinst/openQA/pull/3520
was merged just days ago but that was already deployed at 2020-11-08 01:25:01
says grep 'openQA-worker' /var/log/zypp/history so I see it as unlikely that the issue has been caused directly by that revert.

Acceptance criteria

  • AC1: The s390x test scenarios are not incompleting anymore due to "no WORKER_CLASS defined" on rebel

Suggestions

  • Compare with other workers
  • Check what could cause this, e.g. in /etc/openqa/workers.ini
  • Also look into #77014

Related issues 3 (1 open — 2 closed)

Related to openQA Project - action #77014: openQA webui entry "Assigned worker" shows ip instead of names as formerlyWorkable2020-11-05

Actions
Related to openQA Tests - action #69328: [o3][s390x] Early fail on s390x workers: connection refusedResolvedokurz2020-07-242020-11-13

Actions
Blocks openQA Tests - action #77116: test fails in bootloader_s390 - ftp installation media directory repo is too long for using in parmfile - linux144, linux145, linux146, linux147 (rebel)ResolvedSLindoMansilla2020-11-08

Actions
Actions
Copy link

Also available in: Atom PDF