Project

General

Profile

Actions
Copy link

action #165515

open

Avoid 502 respones by signaling readiness of the main openQA service to systemd and starting it `Before=nginx.service`

Added by mkittler 4 months ago. Updated 4 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA (public) - future
Start date:
2024-08-20
Due date:
% Done:

0%

Estimated time:

Description

Motivation

After #128318 there are still a few 502 responses left (not enough to trigger the alert). Those would happen on reboots where nginx.service can be started before openqa-webui.service is ready. Doing as the ticket title says would help with that.

Acceptance criteria

  • AC1: There are no more 502 responses for routes of the main openQA service caused by rebooting the main web UI VM.

Suggestions

  • Read #162533#note-31 for an idea how to approach this.
  • Use a query like this example to view the 5xx responses in a certain time frame (to check whether the change you came up with actually helped).
  • Possibly also come up with a solution that can be (re-)used in the other micro services - even though the focus is on the main openQA service.
Actions
Copy link
 #1

Updated by okurz 4 months ago

  • Priority changed from Normal to Low
  • Target version set to future
Actions
Copy link

Also available in: Atom PDF