Actions
action #174610
closed[alert] salt-states-openqa deploy pipeline failed: data failed to compile
Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-12-19
Due date:
% Done:
0%
Estimated time:
Tags:
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 ...
^
Updated by jbaier_cz about 1 month ago
- Related to action #168811: baremetal-support in PRG2 size:M added
Updated by dheidler about 1 month ago
- Status changed from New to In Progress
- Assignee set to dheidler
Updated by dheidler about 1 month 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
Updated by dheidler about 1 month ago
- Status changed from In Progress to Resolved
Updated by jbaier_cz about 1 month 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
Updated by jbaier_cz about 1 month ago
- Related to action #174652: Ensure uniqueness of nodenames for generating configs on monitor size:M added
Actions