OhMyBug

config/deploy

Rollout assumes only new code runs

rare73 sightingsfirst seen September 2026

What goes wrong

A change is written as if the switch from the old version to the new one happens in a single instant. During a rollout both versions serve the same traffic and the same stored state, so the old one keeps doing what the change assumed had already stopped. The author relies on deployment being atomic when it is gradual.

Example

A release stops writing a marker that the previous version still requires, and every request that lands on a not-yet-replaced instance fails until the last one is gone.

Not to be confused with

Not accepted setting silently inert: both versions here behave exactly as written, and the fault is that two generations of behaviour are live at the same moment.

Discovered by

Field notes · 4

Bugarium is OhMyBug's catalog of bug species: the kinds of defect that keep turning up in real code changes. Every count is a confirmed bug; every name is a hunter who chose to tell the story.