Project

General

Profile

Actions

action #161327

closed

coordination #155485: [saga][epic] Efficient openQA worker pool resource handling in datacenters

coordination #162041: [epic] Improved worker behaviour

Prevent remote workers registering as "localhost" size:S

Added by okurz about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Motivation

In #160424 we first estimated with quite some effort what could and should be done but in the end the ticket was resolved after "just" setting static hostnames which we AFAIK have not even mentioned as a practice in openQA documentation. Are we ok with that or can we do better?

Acceptance criteria

  • AC1: Remote worker hosts can only register with a proper hostname and not localhost without needing to hardcode the hostname in workers.ini
  • AC2: There is a clear error message with suggestion on invalid remote worker connection attempts as "localhost"
  • AC3: It is still possible to register as "localhost", e.g. for single instance container setup, when using the loopback interface

Suggestions


Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure - action #160424: o3: arm21 & arm22 show up as "localhost", (almost) all jobs incomplete size:MResolveddheidler2024-05-162024-06-05

Actions
Actions #1

Updated by okurz about 2 months ago

  • Copied from action #160424: o3: arm21 & arm22 show up as "localhost", (almost) all jobs incomplete size:M added
Actions #2

Updated by okurz about 1 month ago

  • Subject changed from Follow-up to "o3: arm21 & arm22 show up as "localhost", (almost) all jobs incomplete" - are we fine to have invested quite some effort for estimating but then just set static hostnames? to Prevent remote workers registering as "localhost" size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #3

Updated by okurz about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz
Actions #4

Updated by okurz about 1 month ago

  • Due date set to 2024-06-24
  • Status changed from In Progress to Feedback
Actions #5

Updated by okurz about 1 month ago

  • Project changed from openQA Infrastructure to openQA Project
  • Category changed from Feature requests to Feature requests
Actions #6

Updated by okurz about 1 month ago

  • Parent task set to #162041
Actions #7

Updated by okurz about 1 month ago

  • Due date deleted (2024-06-24)
  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF