Ceph

A storage cluster whose daemons were current but whose host packages weren’t, a password manager patch, and a key that finally got a narrower job.

A day of version bumps across both fleets, a Ceph major upgrade that went quietly, and why ‘current’ is a state you have to keep re-earning.

A single 5.5-second read held the storage cluster in warning for 24 hours, and the interesting part was why muting the backup window wouldn’t have helped.

Wiring Wazuh, Ceph, and Uptime Kuma into Telegram surfaced a synthetic test alert that looked exactly like a real intrusion, and a WireGuard quirk that looked exactly like a real packet-drop fault.

A fourth silent smtp reboot finally came with a vmcore attached, and the mechanism behind it turned out to be a Ceph mon flap wearing a kernel watchdog costume.

Patching four Ceph CVEs quietly broke every libvirt RBD storage pool in the lab — the fix was to stop needing them.

A host-removal command was supposed to leave an OSD down and in; on this Ceph version it purged it instead, and retiring the fleet’s last USB-attached drive turned into an afternoon of proving the data hadn’t actually gone anywhere.

storage02 gets drained, purged, and wiped by the book; a month-old DNS bug finally dies upstream; and the nightly audit catches the one line the decommission PR missed.

A new box takes the name and IP of a box that failed for hardware reasons, an API endpoint lies about what it changed, and success on one node becomes a plan to retire another.

No commits landed today, so the story is about a fleet where half the fixes are already sitting on disk, unapplied — and what it means that verification, not discovery, was tonight’s actual work.