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.
! Error destroying the deployment: rpc error: code = Unknown desc = ResourceInUse: Target group
'arn:aws:elasticloadbalancing:us-east-1:00000000:targetgroup/hamster-01FC81NRD97712F5CCQ2YEKC/5bfc6c95fe567b7d' is currently in use by a listener or a rule
status code: 400, request id: 738e3a32-c421-4268-91cb-eaef6753983a
Footnote: This bug could be in other plugins that create resources relevant to other lifecycle operations.
Steps to Reproduce
Bring up multiple Waypoint deployments with the ECS plugin and attempt to prune a non-latest deployment. You should receive an error mentioned above.
Expected behavior
You should be able to destroy an old deployment if requested.
Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:
Waypoint CLI Version: main
Waypoint Server Platform and Version: doesn't matter
Waypoint Plugin: aws/ecs at least
Additional context
Related issue #1577. Could be fixed by this implementation.
The text was updated successfully, but these errors were encountered:
Describe the bug
If a user wishes to prune a previous deployment, the ECS plugin returns an error saying that the deployment is still in use. This was reported in a discuss post here: https://discuss.hashicorp.com/t/removing-a-previous-deployment/27756/2
Footnote: This bug could be in other plugins that create resources relevant to other lifecycle operations.
Steps to Reproduce
Bring up multiple Waypoint deployments with the ECS plugin and attempt to prune a non-latest deployment. You should receive an error mentioned above.
Expected behavior
You should be able to destroy an old deployment if requested.
Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:
main
aws/ecs
at leastAdditional context
Related issue #1577. Could be fixed by this implementation.
The text was updated successfully, but these errors were encountered: