Spinnaker "Exception ( Monitor Deploy )" in CI

The Deploy stage submits the operation to Clouddriver, then a "Monitor Deploy" task polls it to completion. This exception means the operation was accepted but the monitor observed the deploy fail, so it is a real deploy error, not a submission error.

What this error means

A Spinnaker deploy stage shows "Exception ( Monitor Deploy )" with a Clouddriver task id. The kato/orchestration task underneath usually carries the concrete reason.

Exception ( Monitor Deploy )
Deploy operation failed:
Failed to deploy server group in prod: 1 error occurred.

Common causes

The provider rejected the deploy operation

Clouddriver accepted the task but the cloud provider (Kubernetes, EC2) rejected the resource, so the monitor task records failure.

The new server group never became healthy

Instances launched but failed health checks within the window, so Monitor Deploy times out and reports the operation failed.

How to fix it

Read the Clouddriver task detail

1. Expand the stage and open the linked Clouddriver task id.
2. Read the kato operation error (quota, image not found, health check).
3. Fix that provider-level cause and re-run the pipeline from CI.

Verify health check and capacity settings

If instances launch but never pass health checks, correct the health check path/port or capacity so the server group can reach healthy state.

How to prevent it

• Keep health check endpoints and ports correct for the deployed app.
• Right-size capacity so the target instance count is actually reachable.
• Alert on Clouddriver task failures so CI-triggered deploys surface fast.

Related guides