tcvcs-cache worker type not using latest docker worker AMIs

RESOLVED FIXED

Status

RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: pmoore, Assigned: garndt)

Tracking

Details

I noticed tcvcs-cache uses different AMIs to other worker types, and I'm not sure why. Rather than upgrade and potentially cause a problem, I thought better to create a bug as garndt is on PTO at the moment, and might know the reason.
Flags: needinfo?(garndt)
  "regions": [
    {
      "region": "us-east-1",
      "secrets": {},
      "scopes": [],
      "userData": {},
      "launchSpec": {
        "ImageId": "ami-b7a321a0"
      }
    },
    {
      "region": "us-west-1",
      "secrets": {},
      "scopes": [],
      "userData": {},
      "launchSpec": {
        "ImageId": "ami-2ec2844e"
      }
    },
    {
      "region": "us-west-2",
      "secrets": {},
      "scopes": [],
      "userData": {},
      "launchSpec": {
        "ImageId": "ami-3bf0325b"
      }
    }
  ],
(Assignee)

Comment 2

2 years ago
These should be able to use the latest amis that are generated.  They were originally patched to fix a problem with the code around taskcluster-proxy but that AMI wasn't rolled out to any others.  that is the only reason for the difference.
Flags: needinfo?(garndt)
I've updated to:

  "regions": [
    {
      "region": "us-east-1",
      "secrets": {},
      "scopes": [],
      "userData": {},
      "launchSpec": {
        "ImageId": "ami-ab3fb1bc"
      }
    },
    {
      "region": "us-west-1",
      "secrets": {},
      "scopes": [],
      "userData": {},
      "launchSpec": {
        "ImageId": "ami-355a1b55"
      }
    },
    {
      "region": "us-west-2",
      "secrets": {},
      "scopes": [],
      "userData": {},
      "launchSpec": {
        "ImageId": "ami-8878b5e8"
      }
    }
  ],


By the way, how do we clean up old (unused) AMIs? Will that happen automatically?
Greg,

In other words, should I delete these AMIs?

  * ami-b7a321a0
  * ami-2ec2844e
  * ami-3bf0325b
Flags: needinfo?(garndt)
(Assignee)

Comment 5

2 years ago
Yes, you should be able to.
Flags: needinfo?(garndt)
(Assignee)

Comment 6

2 years ago
These worker types have been updated multiple times so they should be up-to-date
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.