Root cause: HA runtime template contexts (shell_command {{ }} rendering) cannot read secrets.yaml — kuma_push_url rendered undefined on every fire (logged as a template warning) and the Kuma push dead-man has never sent a beat (matching monitor PFV HA heartbeat (dead-man) = 100% down since creation).
Fix: the full curl command moves into the secret (kuma_heartbeat_cmd); shell_command references it with !secret, which is substituted at config parse where secrets work.
**Root cause:** HA runtime template contexts (shell_command `{{ }}` rendering) cannot read secrets.yaml — `kuma_push_url` rendered undefined on every fire (logged as a template warning) and the Kuma push dead-man has never sent a beat (matching monitor PFV HA heartbeat (dead-man) = 100% down since creation).
**Fix:** the full curl command moves into the secret (`kuma_heartbeat_cmd`); shell_command references it with `!secret`, which is substituted at config parse where secrets work.
**Already live:** on-box fix applied + HA core restarted + verification under GLPI CR 21 (https://cmdb.knownelement.com/front/change.form.php?id=21). This PR makes the git copy match the deployed state.
Ticket: https://projects.knownelement.com/issues/811
HA runtime template contexts (shell_command {{ }} rendering) cannot read
secrets.yaml; kuma_push_url rendered undefined every fire and the Kuma
push dead-man never sent a beat. Move the full curl command into the
secret (kuma_heartbeat_cmd) and reference it with !secret, which is
substituted at config parse where secrets work.
On-box fix applied + verified under GLPI CR 21; this commit makes the
git copy match the deployed state.
Ticket: https://projects.knownelement.com/issues/811
CR: https://cmdb.knownelement.com/front/change.form.php?id=21
ic-reviewer: root cause verified against HA logs (template warning + zero beats since monitor creation); !secret at parse time is the correct pattern. On-box deployed state matches this diff byte-for-byte.
ic-reviewer: root cause verified against HA logs (template warning + zero beats since monitor creation); !secret at parse time is the correct pattern. On-box deployed state matches this diff byte-for-byte.
manager-tsg secondary: alerting-path fix, no behavior change beyond the dead-man actually firing now. LEAVING UNMERGED for the founder release stack (deploys to prod on release merge).
manager-tsg secondary: alerting-path fix, no behavior change beyond the dead-man actually firing now. LEAVING UNMERGED for the founder release stack (deploys to prod on release merge).
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Root cause: HA runtime template contexts (shell_command
{{ }}rendering) cannot read secrets.yaml —kuma_push_urlrendered undefined on every fire (logged as a template warning) and the Kuma push dead-man has never sent a beat (matching monitor PFV HA heartbeat (dead-man) = 100% down since creation).Fix: the full curl command moves into the secret (
kuma_heartbeat_cmd); shell_command references it with!secret, which is substituted at config parse where secrets work.Already live: on-box fix applied + HA core restarted + verification under GLPI CR 21 (https://cmdb.knownelement.com/front/change.form.php?id=21). This PR makes the git copy match the deployed state.
Ticket: https://projects.knownelement.com/issues/811
HA runtime template contexts (shell_command {{ }} rendering) cannot read secrets.yaml; kuma_push_url rendered undefined every fire and the Kuma push dead-man never sent a beat. Move the full curl command into the secret (kuma_heartbeat_cmd) and reference it with !secret, which is substituted at config parse where secrets work. On-box fix applied + verified under GLPI CR 21; this commit makes the git copy match the deployed state. Ticket: https://projects.knownelement.com/issues/811 CR: https://cmdb.knownelement.com/front/change.form.php?id=21ic-reviewer: root cause verified against HA logs (template warning + zero beats since monitor creation); !secret at parse time is the correct pattern. On-box deployed state matches this diff byte-for-byte.
manager-tsg secondary: alerting-path fix, no behavior change beyond the dead-man actually firing now. LEAVING UNMERGED for the founder release stack (deploys to prod on release merge).
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.