Project

General

Profile

Actions

action #157606

open

openQA Project (public) - coordination #112862: [saga][epic] Future ideas for easy multi-machine handling: MM-tests as first-class citizens

openQA Project (public) - coordination #111929: [epic] Stable multi-machine tests covering multiple physical workers

Prevent missing gre tunnel connections in our salt states due to misconfiguration

Added by okurz 9 months ago. Updated 5 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
Category:
Feature requests
Start date:
2024-03-19
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

In #157534 we encountered the case of multi-machine tests failing due to a worker with "tap" class ending up with no GRE tunnel connections to other hosts that participated in cluster tests. This was due to me doing a mistake and using a differing "location-" worker class which is fixed meanwhile but our salt states worker class gre tunnel thingy computation in https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/_modules/gre_peers.py?ref_type=heads was happily putting worker40 in one "cluster" which we should improve to better handle.


Related issues 4 (2 open2 closed)

Related to openQA Project (public) - action #162320: multi-machine test failures 2024-06-14+, auto_review:"ping with packet size 100 failed.*can be GRE tunnel setup issue":retryResolvedokurz2024-06-15

Actions
Related to openQA Infrastructure (public) - action #160826: Optimize gre_tunnel_preup.sh generation jinja template size:SWorkable2024-05-21

Actions
Related to openQA Infrastructure (public) - action #162734: Simple script detecting gre_tunnel_preup.sh with only empty remote_ip= statements during salt CI pipelines size:MWorkable2024-06-21

Actions
Copied from openQA Project (public) - action #157534: Multi-Machine Job fails in suseconnect_scc due to worker class misconfiguration when we introduced prg2e machinesResolvedokurz2024-03-19

Actions
Actions

Also available in: Atom PDF