action #180122: Run openqa-piworker as part of our infrastructure while still being CC compliant - openQA Infrastructure (public) - openSUSE Project Management Tool

Actions

Copy link

action #180122

open

coordination #161414: [epic] Improved salt based infrastructure management

Run openqa-piworker as part of our infrastructure while still being CC compliant

Added by nicksinger about 1 month ago. Updated about 1 month ago.

Status:

New

Priority:

Normal

Assignee:

Category:

Regressions/Crashes

Target version:

QA (public) - Tools - Next

Start date:

Due date:

% Done:

Estimated time:

Tags:

alert, infra, reactive work

Description

Observation¶

In #178576 we realized the MTU of the NUE2 FC-basement network changed to 1360. According to tests while running the machines, this would require us to use a MTU of 1260 for our wireguard tunnels which is too small for IPv6 to properly work and results in failed systemd services and other problems.
All other machines in FC-basement now use no wireguard tunnel because they can reach OSD directly over secure protocols. The only machine where this apparently is not working is openqa-piworker.qe.nue2.suse.org because salt constantly produces timeouts - we need to find a solution to manage this machine reliable again in our infrastructure.

Suggestions¶

@nicksinger made several changes to the network config on the workers:

Rollback actions¶

Add back to salt and production: salt-key -y -a openqa-piworker.qe.nue2.suse.org

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by nicksinger about 1 month ago

Copied from action #178576: Workers unresponsive in salt pipelines including openqa-piworker, sapworker1 and monitor size:S added

Actions

Copy link

Updated by okurz about 1 month ago

Subject changed from Run openqa-piworker as part of our infrastructure while still being CC compliant size:S to Run openqa-piworker as part of our infrastructure while still being CC compliant

Actions

Copy link