Project

General

Profile

Actions
Copy link

action #174610

closed

[alert] salt-states-openqa deploy pipeline failed: data failed to compile

Added by jbaier_cz 7 days ago. Updated 6 days ago.

Status:
Resolved
Priority:
High
Assignee:
dheidler
Category:
Regressions/Crashes
Target version:
openQA Project (public) - Ready
Start date:
2024-12-19
Due date:
% Done:

0%

Estimated time:
Tags:
alert, infra, reactive work

Description

Observation

See: https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/3565629

monitor.qe.nue2.suse.org:
    Data failed to compile:
----------
    Rendering SLS 'base:monitoring.grafana' failed: while constructing a mapping
  in "<unicode string>", line 15, column 1:
    grafana:
    ^
found conflicting ID '/var/lib/grafana/dashboards/generic-baremetal-support.json'
  in "<unicode string>", line 921, column 1:
    /var/lib/grafana/dashboards/gene ... 
    ^

Related issues 2 (1 open — 1 closed)

Related to openQA Infrastructure (public) - action #168811: baremetal-support in PRG2 size:MResolveddheidler2024-02-15

Actions
Related to openQA Infrastructure (public) - action #174652: Use fqdn instead of nodename for generating configs on monitorNew2024-12-20

Actions
Actions
Copy link
 #1

Updated by jbaier_cz 7 days ago

Actions
Copy link
 #2

Updated by jbaier_cz 7 days ago

  • Target version set to Ready
Actions
Copy link
 #3

Updated by dheidler 6 days ago

  • Status changed from New to In Progress
  • Assignee set to dheidler
Actions
Copy link
 #4

Updated by dheidler 6 days ago

Turns out that nodename != minion_id:

As to be seen with 

salt-call mine.get 'not G@roles:webui and not G@roles:worker' 'nodename' tgt_type='compound'

So I did this:

baremetal-support:~ # cat /etc/salt/grains
nodename: baremetal-support-prg2
Actions
Copy link
 #5

Updated by dheidler 6 days ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #6

Updated by jbaier_cz 6 days ago

The down side of this fix is, that now we have a grafana dashboard for baremetal-support-prg2, but obviously no data are collected for that machine as the fqdn is different. As I hate to be the one reopening tickets, I guess we can handle that as part of #174652

Actions
Copy link
 #7

Updated by jbaier_cz 6 days ago

  • Related to action #174652: Use fqdn instead of nodename for generating configs on monitor added
Actions
Copy link

Also available in: Atom PDF