Fix a bug in Service Connect error handling#4588
Merged
Merged
Conversation
singholt
approved these changes
Apr 23, 2025
ShelbyZ
approved these changes
Apr 23, 2025
timj-hh
pushed a commit
to timj-hh/amazon-ecs-agent
that referenced
this pull request
Jul 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Service connect tasks go through an "augmenting" phase handled by
serviceconnect.Manager'sAugmentTaskContainermethod. This method makes some changes to tasks such as populatingAPPNET_CONTAINER_IP_MAPPINGenvironment variable in service connect sidecar container. However, the method implementation currently swallows any errors that happen during the augmentation process. This PR fixes this bug by surfacing any such errors asCannotCreateContainererrors.Testing
Ran a Service Connect bridge mode service task on an instance faked to have IPv6-only compatibility and without IPv6 enabled on docker bridge network. This causes task augmentation to fail because an IPv6 address is expected for each task container but it is not found. Verified the task stop error in DescribeTasks response that is reproduced below.
New tests cover the changes: yes
Description for the changelog
Bugfix: Surface task augmentation errors for Service Connect tasks
Additional Information
Does this PR include breaking model changes? If so, Have you added transformation functions?
No
Does this PR include the addition of new environment variables in the README?
No
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.