Closed
Bug 1466686
Opened 7 years ago
Closed 7 years ago
AWS provisioner worker status page lists inaccurate instance types
Categories
(Taskcluster :: UI, enhancement)
Taskcluster
UI
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1453649
People
(Reporter: gps, Unassigned)
Details
The "Status" tab at e.g. https://tools.taskcluster.net/aws-provisioner/gecko-3-b-linux/ can list inaccurate EC2 instance types after you've updated a worker definition. As a concrete example, I've added c5d instance types to worker definitions, seen c5d instances advertised in the status tab, and opened the AWS web console only to not find a single c5d instance type instance!
Poking at the JSON API responses, I /think/ we may have code assuming that integer offsets align between the order instance types are defined in the worker definition and what is returned by an API. e.g. if you insert a new instance type - say c5d.4xlarge - as the first type in the worker definition, workers associated with offset 0 are now listed as c5d.4xlarge instance types in the "Status" tab.
This is a bit annoying when changing worker type definitions because you can't tell what EC2 instance types are actually provisioned. I have to resort to using the AWS web console to obtain this information.
Comment 1•7 years ago
|
||
You'll note that *all* of the numbers in the status page are zero.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: Tools → UI and Tools
You need to log in
before you can comment on or make changes to this bug.
Description
•