Per vidyo & email, plan to unblock ateam testing of panda chassis and followon: Panda chassis "2" (1 of the 5 in the 2nd wave) - use for smoke testing (Joel is contact). Actions needed: - Jake/relops to install image on all 12 boards in that chassis - Jake/relops to provide Callek & Joel with IP addresses for those 12 boards - Callek/Releng to add those 12 pandas to the existing linux foopy - Callek/RelEng to let Joel know when they're ready to go - Joel/ateam - do all the smoketest work on chassis 2

Expect the imaged cards to be put in on the earlier half of Monday. Panda chassis "2": panda-022.build.scl1.mozilla.com 10.12.52.123 panda-023.build.scl1.mozilla.com 10.12.52.124 panda-024.build.scl1.mozilla.com 10.12.52.125 panda-025.build.scl1.mozilla.com 10.12.52.126 panda-026.build.scl1.mozilla.com 10.12.52.127 panda-027.build.scl1.mozilla.com 10.12.52.128 panda-028.build.scl1.mozilla.com 10.12.52.129 panda-029.build.scl1.mozilla.com 10.12.52.130 panda-030.build.scl1.mozilla.com 10.12.52.131 panda-031.build.scl1.mozilla.com 10.12.52.132 panda-032.build.scl1.mozilla.com 10.12.52.133 panda-033.build.scl1.mozilla.com 10.12.52.134

Just FTR, I am using the image from https://bugzilla.mozilla.org/show_bug.cgi?id=780233#c2 SHA1: adb978807bf85b271fa7ca7f468d7ed4dd210478 /home/jake/panda_2gb.img.bz2

All pandas are up in Chassis "2": Starting Nmap 6.01 ( http://nmap.org ) at 2012-09-10 16:01 PDT Nmap scan report for panda-022.build.scl1.mozilla.com (10.12.52.123) Host is up (0.024s latency). Nmap scan report for panda-023.build.scl1.mozilla.com (10.12.52.124) Host is up (0.020s latency). Nmap scan report for panda-024.build.scl1.mozilla.com (10.12.52.125) Host is up (0.020s latency). Nmap scan report for panda-025.build.scl1.mozilla.com (10.12.52.126) Host is up (0.020s latency). Nmap scan report for panda-026.build.scl1.mozilla.com (10.12.52.127) Host is up (0.020s latency). Nmap scan report for panda-027.build.scl1.mozilla.com (10.12.52.128) Host is up (0.020s latency). Nmap scan report for panda-028.build.scl1.mozilla.com (10.12.52.129) Host is up (0.020s latency). Nmap scan report for panda-029.build.scl1.mozilla.com (10.12.52.130) Host is up (0.020s latency). Nmap scan report for panda-030.build.scl1.mozilla.com (10.12.52.131) Host is up (0.020s latency). Nmap scan report for panda-031.build.scl1.mozilla.com (10.12.52.132) Host is up (0.019s latency). Nmap scan report for panda-032.build.scl1.mozilla.com (10.12.52.133) Host is up (0.028s latency). Nmap scan report for panda-033.build.scl1.mozilla.com (10.12.52.134) Host is up (0.024s latency). Nmap done: 12 IP addresses (12 hosts up) scanned in 0.06 seconds

What are the next steps here?

I am running smoketests on the above mentioned ip addresses. Things are looking good from my end.

Melissa pointed out that this bug is the one that releng is waiting on to run staging runs for panda jobs.

yeah, my bad for not updating this bug. I can reliably run a single pass of the smoketest. There are problems when I run this in a loop I find that I get two sutagentandroid processes which prevents me from rebooting. I can reproduce this locally and have been debugging. This is my #1 priority and is going pretty slow.

I have finished my smoketest work, things have worked out well.