IMPORTANT: Broken ecs-init-1.17.3 on @amzn-updates. about amazon-ecs-init HOT 5 CLOSED

@aaithal @nmeyerhans Thank you for the information!

Our servers were affected by this, but we don't have any automatic yum cron updates running.
Does ECS update its services with the latest ECS Agent? Is there a way to stop this from happening?

from amazon-ecs-init.

Hi @omeid,

Between 4:21 PM and 10:56 PM PDT some customers experienced increased error rates while downloading Amazon ECS agent version 1.17.3. The issue has been resolved and the service is operating normally.

Thanks,
Anirudh

from amazon-ecs-init.

I am sorry but I just checked and ecs-init-1.17.3 is still in @amzn-updates.

Also, how did this all happen? How can a single detached commit without a release tag cause a release that ends up in @amzn-updates?

from amazon-ecs-init.

@omeid, to clarify, ECS Agent 1.17.3 is now available, so ecs-init-1.17.3 from the @amzn-updates repository works. See the agent release for details on that.

As to how ecs-init-1.17.3 was created before the PR was merged, our release process involves building and testing the packages before we actually merge the change. This way if we do need to make any updates to the candidate, we can do so without worrying about invalidating tags or GitHub releases. When the package is released, its corresponding commit is merged into master and tagged appropriately.

from amazon-ecs-init.

Thanks for the clarification Noah,

I think a little more visibility into the release process would be helpful.

As you can see I am watching this repository and yet had no idea to expect an update and it was a fair bit of debugging frustration to find out what is exactly going on.

Have a great weekend.

from amazon-ecs-init.