Project

General

Profile

Actions

action #162377

closed

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

incomplete config files on OSD due to salt - Prevent conflicting state applications on OSD "fstab" size:S

Added by okurz 13 days ago. Updated 10 days ago.

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

0%

Estimated time:

Description

Motivation

See #161324 . Why did salt not manage to update three configuration files in the first place? Maybe this is due the secondary, unlikely hypothesis of "filesystem corruption" we might have had. If not we could reconsider how we write those three specific configuration files which are /etc/openqa/database.ini and /etc/openqa/openqa.ini . okurz thinks at least for /etc/fstab we have two states concerning this file. Maybe it's better to combine those into one

Acceptance criteria

  • AC1: salt state deploy pipelines do not mention recurring updates on "fstab" in no-op calls

Suggestions

  • Take a look how in https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/2732256#L380 it is mentioned that a line is removed in "fstab" even though there are no related changes recently in our salt states. This change is due to fstab being deployed as a complete file by salt and then updated in another state. Probably it's better to combine those into one
  • Avoid mount.mounted and use /etc/fstab instead to avoid the issue

Related issues 1 (1 open0 closed)

Copied from openQA Infrastructure - action #161423: incomplete config files on OSD due to salt - Improve salt state application from remotely accessible salt masterWorkableokurz2024-06-03

Actions
Actions

Also available in: Atom PDF