Closed Bug 1027437 Opened 8 years ago Closed 8 years ago

add more slave names to non jacuzzi builders


(Release Engineering :: General, defect, P1)


(Not tracked)



(Reporter: jlund, Assigned: rail)




(2 files)

we had a tree closure lasting over a few hours due to aws pending jobs (compile/build jobs) not finding a valid spot.

Theories included spot bidding prices being too high, not enough ip's in the AZ subnet group, and not enough slave names for non jacuzzi builders.

Patches were put in place for the first two theories but it seems like only upping the ondemand limit actually solved the issue. This is of course is not a solution so we should look at adding more slave names to our non-jacuzzi builders.

Apparently we added locked a lot of slaves to our jacuzzis in the the last week and this closure may be the result of that bug.

see for more details
also rail, we added a subnet that appeared missing in our config for east-1c:

and, we should probably revert these two band aid fixes once we fix this bug:
Assignee: nobody → rail
Severity: normal → major
Priority: -- → P1
Attached patch spots.diffSplinter Review
Once this is in production I'll need to add the slave to slavealloc, that's it.
Attachment #8442882 - Flags: review?(catlee)
Attachment #8442882 - Flags: review?(catlee) → review+
Attached file spot-bld.csv
To be added to slavealloc
(In reply to Rail Aliiev [:rail] from comment #5)
> Created attachment 8442900 [details]
> spot-bld.csv
> To be added to slavealloc

buildbot-config patch live in production :)
Closed: 8 years ago
Resolution: --- → FIXED
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.