Discover RDS deploys version out of sync with deployment updater #46625
Labels
aws
Used for AWS Related Issues.
bug
database-access
Database access related issues and PRs
discover
Issues related to Teleport Discover
I had an ECS cluster deployed via the integration already, but I had manually scaled the service tasks to 0.
In the background, the AWS OIDC integration updater checks if it should update ECS task definitions to a newer version of Teleport. It checks for a cluster maintenance window every 30 minutes, and if it's in the window then it updates ECS deployments.
In this case, this morning the auto-updater created a new task revision for v16.3.0 and updated my ECS cluster to use the new revision. The prior revision used v16.2.2.
Today, I went through the discover flow again, and when I clicked "Deploy Teleport Service" it updated my ECS cluster service to run 2 tasks again, but it also created a new task definition that again used v16.2.2.
So the ECS task definition revisions look like this:
revision 1: teleport v16.2.2 (from when I created it the first time)
revision 2: teleport v16.3.0 (auto-updater created this morning)
revision 3: teleport v16.2.2 (redeployed teleport service this afternoon)
I found it quite surprising that my ECS service was downgraded.
We need to make sure the service deployment version matches what we use for the auto-updater.
Bug details:
The text was updated successfully, but these errors were encountered: