Closed
Bug 1410110
Opened 7 years ago
Closed 7 years ago
determine if cloudtools watch_pending is still accurate post latest tcmigration cleanup
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Assigned: aobreja)
References
Details
we should ensure that our monitoring tools (watch pending) are accurately showing pool sizes and available aws instances we have since we have disabled >1000 from bug 1393774
Reporter | ||
Updated•7 years ago
|
Blocks: tcmigration_cleanup
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → aobreja
Assignee | ||
Comment 1•7 years ago
|
||
Checked logs and some reports (eg.. [1]) also the spot instances that were created in AWS and the conclusion is that watch_pending is still accurate.
[1] https://secure.pub.build.mozilla.org/buildapi/recent/tst-linux64-spot?numbuilds=1000
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•7 years ago
|
||
\o/ thanks!
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•