deleting rules file breaks refresh_rules.sh
Bug #1775740 reported by
Paul Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Prometheus Charm |
Confirmed
|
Medium
|
Unassigned | ||
Prometheus2 charm |
Fix Released
|
Medium
|
Jacek Nykis |
Bug Description
When a rules file is deleted, check-config fails on the new rules because prometheus.yml still refers to the now-deleted file, which makes such changes difficult to deploy automatically.
Related branches
~jacekn/charm-prometheus2:master
Merged
into
~prometheus-charmers/charm-prometheus2:master
at
revision 2b3cc7365bd880759e3103258d36f693b51ede0e
- Prometheus Charmers: Pending requested
-
Diff: 45 lines (+14/-7)1 file modifiedreactive/prometheus.py (+14/-7)
Changed in prometheus-charm: | |
assignee: | nobody → Jacek Nykis (jacekn) |
assignee: | Jacek Nykis (jacekn) → nobody |
Changed in prometheus-charm: | |
assignee: | nobody → Jacek Nykis (jacekn) |
affects: | prometheus-charm → prometheus2-charm |
Changed in prometheus-charm: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in prometheus2-charm: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
AFAIR update-status will "fix" config automatically. But it's still a valid bug of course, refresh_rules.sh should be improved.