Severity
1 customer reported
Version
2026.3.12104
Latest Version
I could reproduce the problem in the latest build
What happened?
Our Deploy and Update ECS Service steps have incorrect package references after they are updated. Older ECS steps now ask for two packages during release creation. The steps contain a package reference for both the 'Container Name' and 'Package ID' fields. The 'Container Name' field is only meant to match the name of the container in the ECS task definition, so it should not be a separate package reference in Octopus. Adding a new ECS step to a project does not appear to exhibit the same behavior.
Reproduction
Could not reproduce, as it appears to affect only pre-existing steps.
Error and Stacktrace
More Information
Container Definition:
Create Release:
Workaround
It's possible to update the deployment process via the API to remove the duplicate package reference. Please contact support@octopus.com for more information.
Severity
1 customer reported
Version
2026.3.12104
Latest Version
I could reproduce the problem in the latest build
What happened?
Our Deploy and Update ECS Service steps have incorrect package references after they are updated. Older ECS steps now ask for two packages during release creation. The steps contain a package reference for both the 'Container Name' and 'Package ID' fields. The 'Container Name' field is only meant to match the name of the container in the ECS task definition, so it should not be a separate package reference in Octopus. Adding a new ECS step to a project does not appear to exhibit the same behavior.
Reproduction
Could not reproduce, as it appears to affect only pre-existing steps.
Error and Stacktrace
More Information
Container Definition:
Create Release:
Workaround
It's possible to update the deployment process via the API to remove the duplicate package reference. Please contact support@octopus.com for more information.