Closed Bug 1249430 Opened 8 years ago Closed 8 years ago

Return 400 if a workerType is submitted that doesn't have a valid AMI

Categories

(Taskcluster :: Services, defect)

Product:
Taskcluster
Component:
Services
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1159637

People

(Reporter: selenamarie, Unassigned)

References

Details

Per discussion today about busted AMIs ending up in workerTypes.
Should we also mark a worker type (somehow) as disabled, if the AMI is dropped at a later point in time? If so, we should probably work out how to display it differently in the UI, and also work out how we want to monitor/alert on it.

I'll also raise a separate bug about fixing the script in generic worker to reverse the order of deleting old ami and updating worker type with new ami during worker-type update process...
See Also: → 1249581
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Component: AWS-Provisioner → Services
You need to log in before you can comment on or make changes to this bug.