[01:13:06] <shinken-wm>	 PROBLEM - Long lived cherry-picks on puppetmaster on deployment-puppetmaster is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0]
[01:28:25] <shinken-wm>	 PROBLEM - Puppet staleness on deployment-imagescaler01 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [43200.0]
[04:05:11] <wmf-insecte>	 Project selenium-MultimediaViewer » safari,beta,OS X 10.9,contintLabsSlave && UbuntuTrusty build #115: 04FAILURE in 9 min 10 sec: https://integration.wikimedia.org/ci/job/selenium-MultimediaViewer/BROWSER=safari,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=OS%20X%2010.9,label=contintLabsSlave%20&&%20UbuntuTrusty/115/
[04:20:10] <wmf-insecte>	 Yippee, build fixed!
[04:20:10] <wmf-insecte>	 Project selenium-MultimediaViewer » chrome,beta,OS X 10.9,contintLabsSlave && UbuntuTrusty build #115: 09FIXED in 24 min: https://integration.wikimedia.org/ci/job/selenium-MultimediaViewer/BROWSER=chrome,MEDIAWIKI_ENVIRONMENT=beta,PLATFORM=OS%20X%2010.9,label=contintLabsSlave%20&&%20UbuntuTrusty/115/
[10:48:20] <grrrit-wm>	 (03PS4) 10Paladox: Add test to verify every extension+skin has an entry in zuul/layout.yaml [integration/config] - 10https://gerrit.wikimedia.org/r/198185 (owner: 10Legoktm)
[10:49:04] <grrrit-wm>	 (03CR) 10jenkins-bot: [V: 04-1] Add test to verify every extension+skin has an entry in zuul/layout.yaml [integration/config] - 10https://gerrit.wikimedia.org/r/198185 (owner: 10Legoktm)
[14:58:28] <shinken-wm>	 PROBLEM - Puppet run on deployment-sca02 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0]
[14:59:16] <shinken-wm>	 PROBLEM - Puppet run on deployment-sca01 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0]
[15:57:56] <shinken-wm>	 PROBLEM - Puppet run on integration-slave-trusty-1013 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0]
[20:20:26] <shinken-wm>	 PROBLEM - Host deployment-parsoid05 is DOWN: CRITICAL - Host Unreachable (10.68.16.120)
[21:31:46] <shinken-wm>	 PROBLEM - Puppet run on deployment-aqs01 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0]
[21:34:38] <shinken-wm>	 PROBLEM - Puppet run on integration-slave-precise-1012 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0]
[21:35:43] <shinken-wm>	 PROBLEM - Puppet run on integration-slave-precise-1011 is CRITICAL: CRITICAL: 100.00% of data above the critical threshold [0.0]
[21:58:47] <legoktm>	 chasemp: moving things back to nodepool isn't too hard, it's mostly just reverting the commits that moved them off. But I'm not entirely convinced we even should move them back, many of the jobs that were moved off run in less than a minute, which seems wasteful to spin an entire VM up for.
[22:16:35] <bd808>	 the theory about moving everything to nodepool was that the clean vms would allow removing the trust list for tests. After what nodepool did to our OpenStack though that seems like something that is blocked on hardware and possibly techops to maintain the pool.