You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipeline deployment of the ECS provider succeeds right after the ECS task is up & healthy, but ignores the health status of the LB's Target Group being "Unknown".
Cloud Provider(s):
AWS ECS
Environment:
Spinnaker 1.33.0 (self-hosted on Ubuntu).
Feature Area:
Pipelines.
Description:
The application is configured with the option Consider only cloud provider health when executing tasks disabled, so it should take Load Balancer's Target Group health into account when deploying.
During pipeline deploy, when new sever group is created, Spinnaker proceeds to destroy the old server group right after the ECS task health is Up, despite Load Balancer health still being Unknown.
This leads to traffic being directed to unhealthy instances and alerts from CloudWatch on HealthyHostCount being 0.
ECS task definition does not have its own healthcheck defined.
This used to work correctly before, but I've made a long overdue upgrade from version 1.20 to 1.33.0 and it broke.
Expected behaviour
Old server group is destroyed only after both health checks for the new server group are "Up".
Steps to Reproduce:
Create a deployment pipeline with ECS provider and Highlander strategy.
Execute the pipeline.
The text was updated successfully, but these errors were encountered:
Issue Summary:
Pipeline deployment of the ECS provider succeeds right after the ECS task is up & healthy, but ignores the health status of the LB's Target Group being "Unknown".
Cloud Provider(s):
AWS ECS
Environment:
Spinnaker 1.33.0 (self-hosted on Ubuntu).
Feature Area:
Pipelines.
Description:
The application is configured with the option
Consider only cloud provider health when executing tasks
disabled, so it should take Load Balancer's Target Group health into account when deploying.During pipeline deploy, when new sever group is created, Spinnaker proceeds to destroy the old server group right after the ECS task health is
Up
, despite Load Balancer health still beingUnknown
.This leads to traffic being directed to unhealthy instances and alerts from CloudWatch on
HealthyHostCount
being 0.ECS task definition does not have its own healthcheck defined.
This used to work correctly before, but I've made a long overdue upgrade from version 1.20 to 1.33.0 and it broke.
Expected behaviour
Old server group is destroyed only after both health checks for the new server group are "Up".
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: