Skip to content
Agent Fleet

v0.9.2

A follow-up to the EC2-backed persistent workspaces of 0.9.0, from running one as a real deployment: a home created from the pre-baked golden snapshot could not start at all, and baking a golden by hand ran into a step that never completes.

New

Section titled “New”
  • The Control Plane re-bakes the golden snapshot when the workspace image changes. Re-baking used to be a manual step tied to each release, and the only sign it had been forgotten was a warning in the log. The Control Plane now boots a reserved seed, captures its home as a candidate, boots a second reserved member from it, and publishes the candidate only once that one has come up — a candidate that will not boot is kept and marked rejected with the reason. The bake will not begin while the pool has fewer than two free slots, and gives up on an image after two failed candidates. AF_ECS_EC2_GOLDEN_AUTOBAKE=0 switches it off.

Fixed

Section titled “Fixed”
  • A home created from a golden snapshot never started — the task restarted forever, and no log said why. A golden home arrives with the seed’s links already in place while a brand-new user’s keep volume is empty, so the entrypoint pointed ~/.config at nothing that existed and took itself down. An empty home could never hit it, so it appeared exactly where a deployment starts serving new users from a golden.
  • A workspace whose Start failed before its home volume existed was retried once a minute, forever. Expiry was measured from the volume’s creation time, so a row created without one had no clock to expire against; it now falls back to the workspace’s own creation time.
  • Baking a golden by hand could not be finished as documented. The procedure said to wait for the sweeper to release the slot, but Stop leaves the home attached, so bake-golden.sh refused the slot no matter how long you waited. It now refuses a slot only while its instance is running. The instructions were corrected against measurement as well: the wait scales with the blocks actually used, a seed has to be a member who can sign in, and no repository may be cloned into the seed.

Upgrade notes

Section titled “Upgrade notes”

Nothing to do outside an ecs-ec2 deployment. There the automatic bake is on from this release, so after you move the image tag expect the Control Plane to spend two pool slots baking a golden and proving it boots. Until it finishes, a new user’s home is built empty — a slow first start, as before the golden existed — because a golden baked from the previous image is refused rather than used.