Closed
Bug 1288527
Opened 8 years ago
Closed 7 years ago
tcvcs-cache worker type not using latest docker worker AMIs
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Assigned: garndt)
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.
Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(garndt)
Reporter | ||
Comment 1•8 years ago
|
||
"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•8 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)
Reporter | ||
Comment 3•8 years ago
|
||
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?
Reporter | ||
Comment 4•8 years ago
|
||
Greg, In other words, should I delete these AMIs? * ami-b7a321a0 * ami-2ec2844e * ami-3bf0325b
Flags: needinfo?(garndt)
Assignee | ||
Comment 6•7 years ago
|
||
These worker types have been updated multiple times so they should be up-to-date
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•