Project

General

Profile

Actions

action #180209

closed

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

Emails not sent to osd-admins for all salt-controlled hosts size:S

Added by dheidler about 1 month ago. Updated 20 days ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Start date:
2025-04-08
Due date:
% Done:

0%

Estimated time:

Description

Motivation

This error is sent to the root account on osd every hour:

touch: cannot touch '/var/lib/openqa/factory/repo/cvd/*': No such file or directory

Acceptance Criteria

  • AC1: Emails are sent to osd-admins for all salt-controlled hosts
  • AC2: The root mailbox is aliased to osd admins

Suggestions

Out of scope

  • Fixing underlying issues we didn't see previously

Related issues 4 (1 open3 closed)

Related to openQA Infrastructure (public) - action #154180: Proper kvm asset cleanup for s390x kvm backend (svirt) and tests size:SBlockedlivdywan

Actions
Related to openQA Infrastructure (public) - action #180980: openqa.suse.de: Cron <geekotest@ariel> ls -t /var/lib/snapshot-changes/kubic/Tumbleweed/* | tail -n +60 | xargs rm -fResolved

Actions
Related to openQA Infrastructure (public) - action #181580: jenkins doesn't notify us on broken builds/runs - should there be e-mails or such? size:SResolvednicksinger2025-04-29

Actions
Copied to openQA Infrastructure (public) - action #180926: openqa.suse.de: Cron <root@openqa> touch /var/lib/openqa/factory/repo/cvd/* size:SResolvedmkittler2025-04-08

Actions
Actions #1

Updated by okurz about 1 month ago

  • Tags set to infra, reactive work, osd
  • Category set to Regressions/Crashes
  • Target version set to Ready
Actions #2

Updated by livdywan about 1 month ago

I suppose this also covers salt pipeline errors related to postfix?

          ID: configure_relayhost
    Function: module.run
      Result: False
     Comment: Unavailable function: postfix.set_main.
     Started: 15:19:18.844958
    Duration: 437.529 ms
     Changes:   
----------
          ID: configure_myhost
    Function: module.run
      Result: False
     Comment: Unavailable function: postfix.set_main.
     Started: 15:19:19.282687
    Duration: 0.581 ms
     Changes:  
Actions #3

Updated by livdywan about 1 month ago

  • Description updated (diff)
Actions #4

Updated by livdywan about 1 month ago

  • Priority changed from Normal to High

Raising prio since this is silently failing and we rely on a working postfix setup elsewhere

Actions #5

Updated by livdywan about 1 month ago

  • Subject changed from openqa.suse.de: Cron <root@openqa> touch /var/lib/openqa/factory/repo/cvd/* to openqa.suse.de: Cron <root@openqa> touch /var/lib/openqa/factory/repo/cvd/* size:S
  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee set to dheidler
Actions #6

Updated by livdywan about 1 month ago

  • Subject changed from openqa.suse.de: Cron <root@openqa> touch /var/lib/openqa/factory/repo/cvd/* size:S to Emails not sent to osd-admins for all salt-controlled hosts size:S
Actions #7

Updated by livdywan about 1 month ago

  • Copied to action #180926: openqa.suse.de: Cron <root@openqa> touch /var/lib/openqa/factory/repo/cvd/* size:S added
Actions #8

Updated by mkittler about 1 month ago

https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1431 was merged but caused a few failing pipelines (see mails from GitLab).

We should not probably also look into #154180.

Actions #9

Updated by livdywan about 1 month ago

  • Related to action #154180: Proper kvm asset cleanup for s390x kvm backend (svirt) and tests size:S added
Actions #10

Updated by dheidler about 1 month ago

  • Status changed from In Progress to Resolved
Actions #11

Updated by livdywan about 1 month ago

  • Related to action #180980: openqa.suse.de: Cron <geekotest@ariel> ls -t /var/lib/snapshot-changes/kubic/Tumbleweed/* | tail -n +60 | xargs rm -f added
Actions #12

Updated by okurz 20 days ago

  • Parent task set to #161414
Actions #13

Updated by okurz 20 days ago

  • Related to action #181580: jenkins doesn't notify us on broken builds/runs - should there be e-mails or such? size:S added
Actions

Also available in: Atom PDF