#31 treated any open interface_down alert as "was up". Production had six open alerts that were all created in the same second, 2026-03-02 03:40:53. That points to a monitor glitch, not real failures. They are on ports that were never in use:
large1: enp36s0 and a USB adapter
compute-storage-01: nic1, nic2 and nic3
micro1: enp3s0
Reviving them opened per-host tickets and a P1 cluster-wide ticket (310040512). They also keep updating every poll.
What changes
The #31 merge is reverted, restoring the previous behaviour. A safer fix will follow separately, after the bogus alerts are cleared.
## Why
#31 treated any open `interface_down` alert as "was up". Production had six open alerts that were all created in the same second, 2026-03-02 03:40:53. That points to a monitor glitch, not real failures. They are on ports that were never in use:
- large1: `enp36s0` and a USB adapter
- compute-storage-01: `nic1`, `nic2` and `nic3`
- micro1: `enp3s0`
Reviving them opened per-host tickets and a P1 cluster-wide ticket (310040512). They also keep updating every poll.
## What changes
The #31 merge is reverted, restoring the previous behaviour. A safer fix will follow separately, after the bogus alerts are cleared.
## Testing
370 tests pass, the count before #31.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
#31 treated any open interface_down alert as previously up. Production had
six such alerts all created in the same second on 2026-03-02 (a monitor
glitch, on ports that were never in use: large1 enp36s0 and a USB adapter,
compute-storage-01 nic1-3, micro1 enp3s0). Reviving them opened per-host
tickets and a P1 cluster-wide ticket. Back to the previous behaviour while a
safer fix is worked out.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jared
scheduled this pull request to auto merge when all checks succeed 2026-11-11 01:17:01 -05:00
jared
merged commit fde1d01f27 into main2026-11-11 01:17:47 -05:00
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.
Why
#31 treated any open
interface_downalert as "was up". Production had six open alerts that were all created in the same second, 2026-03-02 03:40:53. That points to a monitor glitch, not real failures. They are on ports that were never in use:enp36s0and a USB adapternic1,nic2andnic3enp3s0Reviving them opened per-host tickets and a P1 cluster-wide ticket (310040512). They also keep updating every poll.
What changes
The #31 merge is reverted, restoring the previous behaviour. A safer fix will follow separately, after the bogus alerts are cleared.
Testing
370 tests pass, the count before #31.
🤖 Generated with Claude Code