Project

General

Profile

Actions

action #109734

closed

Better way to prevent conflicts between openqa-worker@ and openqa-worker-auto-restart@ variants size:M

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

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-04-09
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Multiple times we have found users trying to start the systemd-services openqa-worker@ when instead we are running openqa-worker-auto-restart@. Last instance when that happened was in #109055. We should try to find a better way which is less confusing to users. At best we should have only openqa-worker@ and use configuration to solve the auto-restart requirement.

Acceptance criteria

  • AC1: We have an unambiguous solution for providing both variants of worker modes which are not confusing users
  • AC2: Ensure documentation covers the updated way

Suggestions

  • DONE: Research about systemd service best practices
  • DONE: Research why we chose to have separate systemd service at the time -> Likely because we need different settings on systemd level
  • DONE: Conduct a brainstorming session together, different ideas:
    • Replace openqa-worker@ by a symlink pointing to the real solution, e.g. "openqa-worker-auto-restart" and "openqa-worker-plain", similar to "network.service" which for us is a symlink in /etc/systemd/system pointing to e.g. /usr/lib/systemd/system/NetworkManager.service or /usr/lib/systemd/system/wicked.service
    • Alternative: just provide a drop-in file instead of separate systemd service file
    • Alternative: Potentially provide the drop-in file in an openSUSE package
    • Alternative: Solve it within a process itself so that systemd is not involved, e.g. same as hypnotoad or nginx
  • Should the services be actual "conflicts" on the level of systemd? -> Likely yes, but not a full solution. Could be done on top
  • Update documentation

Related issues 2 (0 open2 closed)

Related to openQA Infrastructure - action #109055: Broken workers alertResolvedokurz2022-03-28

Actions
Related to openQA Project - action #133352: Activating systemd target openqa-worker.target when openqa-worker-auto-restart@ is already used causes havoc size:MResolvedjbaier_cz2023-07-26

Actions
Actions

Also available in: Atom PDF