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
{{ message }}
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Describe the bug
The releaser for AWS ECS plugin checks for unhealthy targets in a target group, but reports healthy if there is no target in the target group at all. The deploy step does not wait for the tasks to be in "running" state before moving to the release step, which at that point in time the tasks (which are in "pending" state) has yet to be registered as targets in the new target group.
Steps to Reproduce
Run waypoint deploy with aws-ecs apps.
Describe the bug
The releaser for AWS ECS plugin checks for unhealthy targets in a target group, but reports healthy if there is no target in the target group at all. The deploy step does not wait for the tasks to be in "running" state before moving to the release step, which at that point in time the tasks (which are in "pending" state) has yet to be registered as targets in the new target group.
Steps to Reproduce
Run
waypoint deploy
withaws-ecs
apps.Despite the ECS task is still starting up and the target group being empty, the release step will reports all targets are healthy:
Expected behavior
The releaser should treat a target group with no targets as "unhealthy", and report that accordingly.
Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:
aws/ecs
Additional context
Relevant code snippet:
waypoint/builtin/aws/ecs/releaser.go
Lines 147 to 158 in d65a8d9
The text was updated successfully, but these errors were encountered: