Spinnaker Rosco "No output ... bake" failure in CI

The Bake stage runs Rosco, which invokes Packer to produce a machine image. "No output" means Packer exited without emitting an artifact, so the bake produced nothing for the deploy stage to consume.

What this error means

A Bake stage fails with "No output from bake" or a Rosco/Packer error. Downstream deploy stages then fail because the baked artifact binding is empty.

Spinnaker

Exception ( Bake )
Error: No output from bake. Rosco job failed:
Build 'amazon-ebs' errored: no base AMI found matching filters

Common causes

The base image or package version does not exist

Rosco could not resolve the base AMI/image or the requested package version, so Packer errored before producing an artifact.

A misconfigured bake template or missing repository

A wrong Packer template, a missing apt/yum repo, or a bad bakery region leaves the bake with no output.

How to fix it

Read the Rosco job log

Open the Bake stage and follow the link to the Rosco job.
Find the Packer build error (missing base image, package not found).
Correct the base image, package version, or template and re-bake.

Pin a valid base image and package repo

Configure the bakery with a base image that exists in the target region and a package repository that serves the requested version.

How to prevent it

Pin base images that exist in the deploy region.
Verify package versions are published before the bake runs.
Keep bakery region and template config in version control.