issue with Scale up or down a service when a failure occurs once it doesn't pull the latest result from AWS ECS.

[kdonekal]

Hi @fabfuel

I encountered a strange issue.

I have the AWS Scale command working fine for sometime.

Due to some ARN permissions issue on the AWS side for the ECS Service it got failed once and after i fixed that issue when I run the below command as in your example

ecs scale my-cluster my-service 4

It keeps throwing the failed cause as an issue but on the AWS side the service is stopping and starting appropriately.

Can you please help me on this.

Thanks,
Kishore D.

[kdonekal]

[fabfuel]

Hi @kdonekal,

thanks for sharing, I have to look into this a bit deeper. The error handling unfortunately is interpretation based on error dates, this might be a bug. I'll reach out, if I need additional infos to reproduce this.

Can you scale normally again or is it still appearing?

Best
Fabian

[kdonekal]

Hi @fabfuel ,

The error is not shown on the AWS console events for the ECS Service scale up and scale down.

But while I run the ecs scale command utility on my local machine or via the Jenkins job its throwing the same OLDER error cause and failing with the ecs scale command utility on the local as well as with my Jenkins job console.

Can you scale normally again or is it still appearing? - To answer this. YES, I could able to scale normally, only issue with the ecs scale command utility for making it sure not to refer any OLDER failures for the latest executions.

let me know if you need more details.

Thanks,
Kishore D.