Skip to main content

My Pipeline Is Stuck On “Wait For Up Instances”

Apr 14, 2017 by Isaac Mosquera

While executing a pipeline you might have run into this issue when not using an ELB where the pipeline gets stuck on “Wait for Up Instances”

Why does this happen?

Spinnaker uses external services such as ELB, Eureka or Consul to determine wether the instance is “up”. Once Spinnaker observes that the instance is “up” it will then “enable” the instance by placing it behind the ELB or enabling it within Eureka/Consul. If you’re not using an ELB or an external service, Spinnaker has no way to determine wether the instance is “up” by default.

How to change this behavior

You can however change this behavior by changing an application’s attributes and making sure that the “Consider Only Cloud Provider Health When Executing Tasks” is checked. This will instead just consider the instance “up” when the cloud provider does its checks and not consider service/application level readiness for health.

For additional information here is what is specified with the helper note from the UI:

When this option is enabled, instance status as reported by the cloud provider will be considered sufficient to determine task completion. When this option is disabled, tasks will normally need health status reported by some other health provider (e.g. a load balancer or discovery service) to determine task completion.

You can find this configuration option within the config section of your app and then by clicking “Edit Application Attributes”

edit application attributes

armory spinnaker

Learn More

Recently Published Posts

July 26, 2021
|
by Phebe Vickers

A day in the life of a TAM

I’ve been asked what a Technical Account Manager (TAM) does so I wanted to take the opportunity to illustrate it by walking through a standard day in the life. Before we can look at what a day in a life of a TAM is, I should provide some background in what is a TAM and […]

Read more

June 29, 2021
|
by Nikema Prophet

Nikema’s Spinnaker Summit 2021 Recap

My Second Spinnaker Summit is in the Books! Last week I attended and spoke at my second Spinnaker Summit. Like last year’s summit, it was fully virtual. This time Spinnaker Summit was co-located with cdCon and took place on the Hopin platform. Last year, I spoke on a panel about Black professionals a few months […]

Read more

June 28, 2021
|
by Stephen Atwell

Announcing General Availability of Armory Policy Engine Plugin

Armory Policy Engine provides support for automating policy compliance with Spinnaker. Policy Engine Plugin is the latest version of Policy Engine and adds support for both advanced role-based access control (RBAC) use-cases and open source Spinnaker. The release of Policy Engine Plugin comes with new documentation, including a library of example policies from across Armory’s […]

Read more