[Rolling Bug] Fix devices which are down. |
||||||||||||
Issue descriptionAs requested by Tien, I am opening up this bug where we can update devices which are down and need to be fixed. The following devices are not pingable, android1758-cros-rack3-host8-router android1758-cros-rack3-host8-pcap chromeos2-row11-rack4-host1-router
,
Aug 11 2016
android1758-cros-rack3-host8-router Done jongkyuj@jongkyuj0:~$ ping android1758-cros-rack3-host8-router PING android1758-cros-rack3-host8-router.cros.corp.google.com (100.107.126.228) 56(84) bytes of data. 64 bytes from dhcp-100-107-126-228.mtv.corp.google.com (100.107.126.228): icmp_seq=1 ttl=60 time=0.835 ms 64 bytes from dhcp-100-107-126-228.mtv.corp.google.com (100.107.126.228): icmp_seq=2 ttl=60 time=0.917 ms
,
Aug 11 2016
android1758-cros-rack3-host8-pcap Done Tien or Bindu will file a bug to add pcap in this rack later on.
,
Aug 11 2016
chromeos2-row11-rack4-host1-router This router has no power and needs to be replaced with another one.
,
Aug 11 2016
chromeos2-row11-rack4-host1-router Done
,
Aug 11 2016
jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack4-host1-router PING chromeos2-row11-rack4-host1-router.cros.corp.google.com (100.115.244.69) 56(84) bytes of data. 64 bytes from 100.115.244.69: icmp_seq=1 ttl=59 time=1.00 ms 64 bytes from 100.115.244.69: icmp_seq=2 ttl=59 time=0.951 ms 64 bytes from 100.115.244.69: icmp_seq=3 ttl=59 time=0.895 ms 64 bytes from 100.115.244.69: icmp_seq=4 ttl=59 time=0.871 ms 64 bytes from 100.115.244.69: icmp_seq=5 ttl=59 time=0.930 ms
,
Aug 12 2016
The following devices are down. 1) android1758-row4-rack3-host4-servo 2) android1758-row4-rack6-host1-router
,
Aug 12 2016
Let's leave this bug open and reuse it to add more Repair Failed/down devices as they come. Thank you!
,
Aug 17 2016
android1758-row4-rack6-host2-router is down.
,
Aug 17 2016
The Ethernet connection got loose. It's up now. jongkyuj@jongkyuj0:~$ ping android1758-row4-rack6-host2-router PING android1758-row4-rack6-host2-router.cros.corp.google.com (100.107.127.146) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-146.mtv.corp.google.com (100.107.127.146): icmp_seq=1 ttl=60 time=0.801 ms 64 bytes from dhcp-100-107-127-146.mtv.corp.google.com (100.107.127.146): icmp_seq=2 ttl=60 time=0.995 ms 64 bytes from dhcp-100-107-127-146.mtv.corp.google.com (100.107.127.146): icmp_seq=3 ttl=60 time=0.704 ms
,
Aug 17 2016
Thank you Paul for checking on android1758-row4-rack6-host2-router quickly. I found one more servo down. chromeos2-row11-rack6-host5-servo
,
Aug 18 2016
chromeos2-row11-rack6-host5-servo, able to ping the servo now. jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack6-host5-servo PING chromeos2-row11-rack6-host5-servo.cros.corp.google.com (100.115.244.135) 56(84) bytes of data. 64 bytes from 100.115.244.135: icmp_seq=1 ttl=59 time=0.750 ms 64 bytes from 100.115.244.135: icmp_seq=2 ttl=59 time=0.781 ms 64 bytes from 100.115.244.135: icmp_seq=3 ttl=59 time=0.787 ms 64 bytes from 100.115.244.135: icmp_seq=4 ttl=59 time=0.743 ms
,
Aug 22 2016
chromeos3-row5-rack1-host1 is on, but NOT pingable. In contrast, chromeos3-row5-rack1-host2 is on and pingable.
,
Aug 22 2016
ping chromeos2-row11-rack1-host1-servo ping: unknown host chromeos2-row11-rack1-host1-servo
,
Aug 22 2016
ping chromeos2-row11-rack1-host1-servo Done jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack1-host1-servo PING chromeos2-row11-rack1-host1-servo.cros.corp.google.com (100.115.244.101) 56(84) bytes of data. 64 bytes from 100.115.244.101: icmp_seq=1 ttl=59 time=0.762 ms 64 bytes from 100.115.244.101: icmp_seq=2 ttl=59 time=0.768 ms 64 bytes from 100.115.244.101: icmp_seq=3 ttl=59 time=0.726 ms 64 bytes from 100.115.244.101: icmp_seq=4 ttl=59 time=0.762 ms
,
Aug 24 2016
android1758-row4-rack5-host3-servo is unpingable. ping android1758-row4-rack5-host3-servo PING android1758-row4-rack5-host3-servo.cros.corp.google.com (100.107.127.135) 56(84) bytes of data. ^C --- android1758-row4-rack5-host3-servo.cros.corp.google.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 2999ms
,
Aug 24 2016
android1758-row4-rack5-host3-servo is unpingable. Done, it's pinable now ping android1758-row4-rack5-host3-servo PING android1758-row4-rack5-host3-servo.cros.corp.google.com (100.107.127.135) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-135.mtv.corp.google.com (100.107.127.135): icmp_seq=1 ttl=62 time=0.702 ms
,
Aug 24 2016
Completed the powerwash on android1758-row4-rack3-host2 per Aashutosh request.
,
Aug 25 2016
chromeos2-row11-rack2-host1 chromeos2-row11-rack2-host1-servo chromeos2-row11-rack3-host3 Above units got reset and reverify from repair failed.
,
Aug 26 2016
android1758-cros-rack2-host2 Done The host got reset. jongkyuj@jongkyuj0:~$ ping android1758-cros-rack2-host2 PING android1758-cros-rack2-host2.cros.corp.google.com (100.107.126.171) 56(84) bytes of data. 64 bytes from dhcp-100-107-126-171.mtv.corp.google.com (100.107.126.171): icmp_seq=6 ttl=60 time=1.60 ms 64 bytes from dhcp-100-107-126-171.mtv.corp.google.com (100.107.126.171): icmp_seq=7 ttl=60 time=1.34 ms 64 bytes from dhcp-100-107-126-171.mtv.corp.google.com (100.107.126.171): icmp_seq=8 ttl=60 time=0.953 ms 64 bytes from dhcp-100-107-126-171.mtv.corp.google.com (100.107.126.171): icmp_seq=9 ttl=60 time=1.20 ms
,
Aug 26 2016
android1758-cros-rack1-host2-servo Done The servo got reset. jongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host2-servo PING android1758-cros-rack1-host2-servo.cros.corp.google.com (100.107.126.141) 56(84) bytes of data. 64 bytes from dhcp-100-107-126-141.mtv.corp.google.com (100.107.126.141): icmp_seq=1 ttl=60 time=0.789 ms 64 bytes from dhcp-100-107-126-141.mtv.corp.google.com (100.107.126.141): icmp_seq=2 ttl=60 time=0.688 ms 64 bytes from dhcp-100-107-126-141.mtv.corp.google.com (100.107.126.141): icmp_seq=3 ttl=60 time=0.683 ms
,
Aug 26 2016
chromeos2-row11-rack3-host2 DOne The host got reset. jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack3-host2 PING chromeos2-row11-rack3-host2.cros.corp.google.com (100.115.244.14) 56(84) bytes of data. 64 bytes from 100.115.244.14: icmp_seq=1 ttl=59 time=0.778 ms 64 bytes from 100.115.244.14: icmp_seq=2 ttl=59 time=0.721 ms 64 bytes from 100.115.244.14: icmp_seq=3 ttl=59 time=0.692 ms
,
Aug 26 2016
chromeos2-row11-rack6-host2 This rack do not have servo. Reverify the host.
,
Aug 29 2016
android1758-row4-rack8-host1 was reset. jongkyuj@jongkyuj0:~$ ping android1758-row4-rack8-host1 PING android1758-row4-rack8-host1.cros.corp.google.com (100.107.127.177) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-177.mtv.corp.google.com (100.107.127.177): icmp_seq=1 ttl=60 time=1.27 ms 64 bytes from dhcp-100-107-127-177.mtv.corp.google.com (100.107.127.177): icmp_seq=2 ttl=60 time=1.29 ms
,
Aug 30 2016
,
Aug 31 2016
router and servo @ chromeos2-row11-rack1-host5 not pingable.
,
Sep 1 2016
The router is pingable but the servo seems to be bad. Reset the servo and still not able to ping.
,
Sep 1 2016
Veyron-Minnie cell, servo is down. ping android1758-row4-rack5-host3-servo PING android1758-row4-rack5-host3-servo.cros.corp.google.com (100.107.127.135) 56(84) bytes of data. ^C --- android1758-row4-rack5-host3-servo.cros.corp.google.com ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 3999ms
,
Sep 1 2016
Router @ android1758-cros-rack1-host2 (Umaro) is failing with the following error. "Unable to find /usr/sbin/iw on android1758-cros-rack1-host2-router" This is missing iw package. I ran it manually and it failed. I was able to run it successfully on other whirlwind. Check if re-imaging helps. Otherwise, please replace it with a new router.
,
Sep 1 2016
android1758-row4-rack5-host3-servo is up now. ING android1758-row4-rack5-host3-servo.cros.corp.google.com (100.107.127.135) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-135.mtv.corp.google.com (100.107.127.135): icmp_seq=1 ttl=60 time=0.765 ms 64 bytes from dhcp-100-107-127-135.mtv.corp.google.com (100.107.127.135): icmp_seq=2 ttl=60 time=0.761 ms 64 bytes from dhcp-100-107-127-135.mtv.corp.google.com (100.107.127.135): icmp_seq=3 ttl=60 time=0.830 ms
,
Sep 1 2016
Replaced the Whirlwind router for android1758-cros-rack1-host2-router jongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host2-router PING android1758-cros-rack1-host2-router.cros.corp.google.com (100.107.126.140) 56(84) bytes of data. 64 bytes from dhcp-100-107-126-140.mtv.corp.google.com (100.107.126.140): icmp_seq=1 ttl=60 time=0.983 ms 64 bytes from dhcp-100-107-126-140.mtv.corp.google.com (100.107.126.140): icmp_seq=2 ttl=60 time=0.908 ms
,
Sep 2 2016
android1758-row4-rack8-host1 got reset. jongkyuj@jongkyuj0:~$ ping android1758-row4-rack8-host1 PING android1758-row4-rack8-host1.cros.corp.google.com (100.107.127.177) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-177.mtv.corp.google.com (100.107.127.177): icmp_seq=1 ttl=60 time=1.17 ms 64 bytes from dhcp-100-107-127-177.mtv.corp.google.com (100.107.127.177): icmp_seq=2 ttl=60 time=1.22 ms 64 bytes from dhcp-100-107-127-177.mtv.corp.google.com (100.107.127.177): icmp_seq=3 ttl=60 time=1.21 ms
,
Sep 7 2016
The hosts that got reset or reverified fron autotest this morning: jongkyuj@jongkyuj0:~$ ping android1758-row4-rack4-host1 PING android1758-row4-rack4-host1.cros.corp.google.com (100.107.127.109) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-109.mtv.corp.google.com (100.107.127.109): icmp_seq=1 ttl=60 time=0.805 ms 64 bytes from dhcp-100-107-127-109.mtv.corp.google.com (100.107.127.109): icmp_seq=2 ttl=60 time=0.841 ms 64 bytes from dhcp-100-107-127-109.mtv.corp.google.com (100.107.127.109): icmp_seq=3 ttl=60 time=0.835 ms ^X64 bytes from dhcp-100-107-127-109.mtv.corp.google.com (100.107.127.109): icmp_seq=4 ttl=60 time=0.756 ms ^C --- android1758-row4-rack4-host1.cros.corp.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3001ms rtt min/avg/max/mdev = 0.756/0.809/0.841/0.039 ms jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ping android1758-row4-rack1-host1 PING android1758-row4-rack1-host1.cros.corp.google.com (100.107.127.61) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-61.mtv.corp.google.com (100.107.127.61): icmp_seq=1 ttl=60 time=0.863 ms 64 bytes from dhcp-100-107-127-61.mtv.corp.google.com (100.107.127.61): icmp_seq=2 ttl=60 time=0.845 ms 64 bytes from dhcp-100-107-127-61.mtv.corp.google.com (100.107.127.61): icmp_seq=3 ttl=60 time=0.839 ms 64 bytes from dhcp-100-107-127-61.mtv.corp.google.com (100.107.127.61): icmp_seq=4 ttl=60 time=0.813 ms ^C --- android1758-row4-rack1-host1.cros.corp.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt min/avg/max/mdev = 0.813/0.840/0.863/0.017 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack1-host1 PING android1758-row4-rack1-host1.cros.corp.google.com (100.107.127.61) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-61.mtv.corp.google.com (100.107.127.61): icmp_seq=1 ttl=60 time=0.813 ms 64 bytes from dhcp-100-107-127-61.mtv.corp.google.com (100.107.127.61): icmp_seq=2 ttl=60 time=0.796 ms 64 bytes from dhcp-100-107-127-61.mtv.corp.google.com (100.107.127.61): icmp_seq=3 ttl=60 time=0.852 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host2 PING android1758-row4-rack2-host2.cros.corp.google.com (100.107.127.81) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-81.mtv.corp.google.com (100.107.127.81): icmp_seq=1 ttl=60 time=1.30 ms 64 bytes from dhcp-100-107-127-81.mtv.corp.google.com (100.107.127.81): icmp_seq=2 ttl=60 time=1.33 ms ^C --- android1758-row4-rack2-host2.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.306/1.320/1.335/0.039 ms jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host1 PING android1758-row4-rack3-host1.cros.corp.google.com (100.107.127.93) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-93.mtv.corp.google.com (100.107.127.93): icmp_seq=1 ttl=60 time=0.871 ms 64 bytes from dhcp-100-107-127-93.mtv.corp.google.com (100.107.127.93): icmp_seq=2 ttl=60 time=1.42 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host2 PING android1758-row4-rack2-host2.cros.corp.google.com (100.107.127.81) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-81.mtv.corp.google.com (100.107.127.81): icmp_seq=1 ttl=60 time=1.33 ms 64 bytes from dhcp-100-107-127-81.mtv.corp.google.com (100.107.127.81): icmp_seq=2 ttl=60 time=1.33 ms
,
Sep 7 2016
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host3 PING android1758-row4-rack2-host3.cros.corp.google.com (100.107.127.85) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-85.mtv.corp.google.com (100.107.127.85): icmp_seq=1 ttl=60 time=0.784 ms 64 bytes from dhcp-100-107-127-85.mtv.corp.google.com (100.107.127.85): icmp_seq=2 ttl=60 time=1.08 ms ^C --- android1758-row4-rack2-host3.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.784/0.935/1.086/0.151 ms jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ping android1758-row4-rack2-host4 PING android1758-row4-rack2-host4.cros.corp.google.com (100.107.127.89) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-89.mtv.corp.google.com (100.107.127.89): icmp_seq=1 ttl=60 time=1.39 ms 64 bytes from dhcp-100-107-127-89.mtv.corp.google.com (100.107.127.89): icmp_seq=2 ttl=60 time=1.30 ms
,
Sep 7 2016
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack5-host2 PING android1758-row4-rack5-host2.cros.corp.google.com (100.107.127.129) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-129.mtv.corp.google.com (100.107.127.129): icmp_seq=1 ttl=60 time=1.17 ms 64 bytes from dhcp-100-107-127-129.mtv.corp.google.com (100.107.127.129): icmp_seq=2 ttl=60 time=1.22 ms ^C --- android1758-row4-rack5-host2.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.171/1.196/1.221/0.025 ms jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ping android1758-row4-rack5-host4 PING android1758-row4-rack5-host4.cros.corp.google.com (100.107.127.137) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-137.mtv.corp.google.com (100.107.127.137): icmp_seq=1 ttl=60 time=1.08 ms 64 bytes from dhcp-100-107-127-137.mtv.corp.google.com (100.107.127.137): icmp_seq=2 ttl=60 time=0.950 ms
,
Sep 7 2016
PING android1758-row4-rack8-host3.cros.corp.google.com (100.107.127.187) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-187.mtv.corp.google.com (100.107.127.187): icmp_seq=1 ttl=60 time=1.85 ms 64 bytes from dhcp-100-107-127-187.mtv.corp.google.com (100.107.127.187): icmp_seq=2 ttl=60 time=1.71 ms ^C --- android1758-row4-rack8-host3.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.713/1.783/1.854/0.082 ms jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ping android1758-row4-rack8-host4 PING android1758-row4-rack8-host4.cros.corp.google.com (100.107.127.192) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-192.mtv.corp.google.com (100.107.127.192): icmp_seq=1 ttl=60 time=2.09 ms 64 bytes from dhcp-100-107-127-192.mtv.corp.google.com (100.107.127.192): icmp_seq=2 ttl=60 time=1.05 ms ^C --- android1758-row4-rack8-host4.cros.corp.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.052/1.571/2.090/0.519 ms jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ping android1758-row4-rack7-host4 PING android1758-row4-rack7-host4.cros.corp.google.com (100.107.127.172) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-172.mtv.corp.google.com (100.107.127.172): icmp_seq=1 ttl=60 time=0.786 ms 64 bytes from dhcp-100-107-127-172.mtv.corp.google.com (100.107.127.172): icmp_seq=2 ttl=60 time=0.832 ms ^C
,
Sep 7 2016
jongkyuj@jongkyuj0:~$ ping android1758-cros-rack1-host5 PING android1758-cros-rack1-host5.cros.corp.google.com (100.107.126.151) 56(84) bytes of data. 64 bytes from dhcp-100-107-126-151.mtv.corp.google.com (100.107.126.151): icmp_seq=1 ttl=60 time=0.797 ms 64 bytes from dhcp-100-107-126-151.mtv.corp.google.com (100.107.126.151): icmp_seq=2 ttl=60 time=0.778 ms
,
Sep 7 2016
jongkyuj@jongkyuj0:~$ ping chromeos1-grover-host10 PING chromeos1-grover-host10.cros.corp.google.com (172.27.214.151) 56(84) bytes of data. 64 bytes from 172.27.214.151: icmp_seq=1 ttl=62 time=1.10 ms 64 bytes from 172.27.214.151: icmp_seq=2 ttl=62 time=1.03 ms 64 bytes from 172.27.214.151: icmp_seq=3 ttl=62 time=0.999 ms ^C --- chromeos1-grover-host10.cros.corp.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.999/1.047/1.108/0.052 ms jongkyuj@jongkyuj0:~$ ping chromeos1-grover-host11 PING chromeos1-grover-host11.cros.corp.google.com (172.27.214.154) 56(84) bytes of data. 64 bytes from 172.27.214.154: icmp_seq=1 ttl=62 time=0.802 ms 64 bytes from 172.27.214.154: icmp_seq=2 ttl=62 time=0.707 ms 64 bytes from 172.27.214.154: icmp_seq=3 ttl=62 time=0.658 ms ^C --- chromeos1-grover-host11.cros.corp.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.658/0.722/0.802/0.063 ms jongkyuj@jongkyuj0:~$ ping chromeos1-grover-host12 PING chromeos1-grover-host12.cros.corp.google.com (172.27.214.157) 56(84) bytes of data. 64 bytes from 172.27.214.157: icmp_seq=1 ttl=62 time=1.67 ms 64 bytes from 172.27.214.157: icmp_seq=2 ttl=62 time=1.62 ms 64 bytes from 172.27.214.157: icmp_seq=3 ttl=62 time=1.59 ms ^C --- chromeos1-grover-host12.cros.corp.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 1.599/1.631/1.671/0.044 ms jongkyuj@jongkyuj0:~$ ^C jongkyuj@jongkyuj0:~$ ping chromeos1-grover-host3 PING chromeos1-grover-host3.cros.corp.google.com (172.27.214.130) 56(84) bytes of data. 64 bytes from 172.27.214.130: icmp_seq=1 ttl=62 time=1.49 ms 64 bytes from 172.27.214.130: icmp_seq=2 ttl=62 time=0.723 ms 64 bytes from 172.27.214.130: icmp_seq=3 ttl=62 time=0.734 ms ^C --- chromeos1-grover-host3.cros.corp.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.723/0.984/1.497/0.364 ms jongkyuj@jongkyuj0:~$ ping chromeos1-grover-host7 PING chromeos1-grover-host7.cros.corp.google.com (172.27.214.142) 56(84) bytes of data. 64 bytes from 172.27.214.142: icmp_seq=1 ttl=62 time=1.57 ms 64 bytes from 172.27.214.142: icmp_seq=2 ttl=62 time=1.60 ms 64 bytes from 172.27.214.142: icmp_seq=3 ttl=62 time=1.80 ms 64 bytes from 172.27.214.142: icmp_seq=4 ttl=62 time=1.46 ms ^C --- chromeos1-grover-host7.cros.corp.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 1.460/1.612/1.807/0.125 ms jongkyuj@jongkyuj0:~$ ping chromeos1-grover-host9 PING chromeos1-grover-host9.cros.corp.google.com (172.27.214.148) 56(84) bytes of data. 64 bytes from 172.27.214.148: icmp_seq=1 ttl=62 time=0.764 ms 64 bytes from 172.27.214.148: icmp_seq=2 ttl=62 time=0.725 ms 64 bytes from 172.27.214.148: icmp_seq=3 ttl=62 time=0.752 ms 64 bytes from 172.27.214.148: icmp_seq=4 ttl=62 time=0.681 ms
,
Sep 13 2016
chromeos2-row11-rack6-host2 chromeos2-row11-rack5-host2 The host got reset and reverifying
,
Sep 13 2016
AP @ http://chromeos3-row4-rack3-host12:8080/ (http://172.22.39.52:8080/) not pingable.
,
Sep 14 2016
The host chromeos3-row4-rack3-host12 is not pingable. This Cisco AP was reset by holding down the reset button from the back of the AP but still not pingable. This host needs to be replaced.
,
Sep 14 2016
chromeos2-row11-rack3-host3 chromeos2-row11-rack6-host2 These hosts got reset and reverifying.
,
Sep 14 2016
Kevin - android1758-cros-rack2-host2 is down.
,
Sep 16 2016
With help from firmware team, just updated the image with 8743.20.0 and latest fw ID 8785.4.2016_09_11_2122 but the Anker 3.0 USB dongle is not recognized.
,
Sep 21 2016
chromeos2-row11-rack3-host3 This host got reset and reverifying. chromeos1-grover-host5 This host got EC reset and reverifying.
,
Sep 26 2016
Can you restart this servo, android1758-row4-rack3-host2-servo. It is pingable but for some reason cannot ssh in it.
,
Sep 26 2016
android1758-row4-rack3-host2-servo Done jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host2-servo PING android1758-row4-rack3-host2-servo.cros.corp.google.com (100.107.127.99) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-99.mtv.corp.google.com (100.107.127.99): icmp_seq=6 ttl=60 time=1.52 ms 64 bytes from dhcp-100-107-127-99.mtv.corp.google.com (100.107.127.99): icmp_seq=7 ttl=60 time=0.793 ms 64 bytes from dhcp-100-107-127-99.mtv.corp.google.com (100.107.127.99): icmp_seq=8 ttl=60 time=0.785 ms ^C
,
Sep 28 2016
android1758-row4-rack7-host1 got reset and in verifying.
,
Sep 28 2016
chromeos2-row11-rack6-host2 in reverifying.
,
Sep 29 2016
android1758-row4-rack8-host1, the host got reset. jongkyuj@jongkyuj0:~$ ping android1758-row4-rack8-host1 PING android1758-row4-rack8-host1.cros.corp.google.com (100.107.127.177) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-177.mtv.corp.google.com (100.107.127.177): icmp_seq=1 ttl=60 time=1.19 ms 64 bytes from dhcp-100-107-127-177.mtv.corp.google.com (100.107.127.177): icmp_seq=2 ttl=60 time=1.35 ms
,
Oct 2 2016
chromeos2-row11-rack6-host2 got reset and reverifying. android1758-row4-rack7-host1 got rteset and reverifying.
,
Oct 3 2016
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack4-host1 PING android1758-row4-rack4-host1.cros.corp.google.com (100.107.127.109) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-109.mtv.corp.google.com (100.107.127.109): icmp_seq=1 ttl=60 time=0.844 ms 64 bytes from dhcp-100-107-127-109.mtv.corp.google.com (100.107.127.109): icmp_seq=2 ttl=60 time=0.809 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack7-host1 PING android1758-row4-rack7-host1.cros.corp.google.com (100.107.127.157) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-157.mtv.corp.google.com (100.107.127.157): icmp_seq=1 ttl=60 time=1.78 ms 64 bytes from dhcp-100-107-127-157.mtv.corp.google.com (100.107.127.157): icmp_seq=2 ttl=60 time=1.47 ms ^C The above hosts got reset.
,
Oct 3 2016
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host4 PING android1758-row4-rack3-host4.cros.corp.google.com (100.107.127.105) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-105.mtv.corp.google.com (100.107.127.105): icmp_seq=1 ttl=60 time=1.42 ms 64 bytes from dhcp-100-107-127-105.mtv.corp.google.com (100.107.127.105): icmp_seq=2 ttl=60 time=1.28 ms 64 bytes from dhcp-100-107-127-105.mtv.corp.google.com (100.107.127.105): icmp_seq=3 ttl=60 time=1.33 ms ^C --- android1758-row4-rack3-host4.cros.corp.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2011ms rtt min/avg/max/mdev = 1.285/1.348/1.423/0.070 ms jongkyuj@jongkyuj0:~$ ping android1758-row4-rack3-host4-servo PING android1758-row4-rack3-host4-servo.cros.corp.google.com (100.107.127.107) 56(84) bytes of data. 64 bytes from dhcp-100-107-127-107.mtv.corp.google.com (100.107.127.107): icmp_seq=1 ttl=60 time=0.842 ms 64 bytes from dhcp-100-107-127-107.mtv.corp.google.com (100.107.127.107): icmp_seq=2 ttl=60 time=0.813 ms 64 bytes from dhcp-100-107-127-107.mtv.corp.google.com (100.107.127.107): icmp_seq=3 ttl=60 time=0.946 ms ^C The host and servo got reset.
,
Oct 3 2016
jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack7-host6 PING chromeos2-row11-rack7-host6.cros.corp.google.com (100.115.244.42) 56(84) bytes of data. 64 bytes from 100.115.244.42: icmp_seq=1 ttl=59 time=1.07 ms 64 bytes from 100.115.244.42: icmp_seq=2 ttl=59 time=0.985 ms The host got reset.
,
Oct 6 2016
chromeos2-row11-rack4-host1-servo is down.
,
Oct 10 2016
chromeos9-row1-cart2-host2-servo is down
,
Oct 10 2016
chromeos2-row11-rack4-host1-servo is up now. jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack4-host1-servo PING chromeos2-row11-rack4-host1-servo.cros.corp.google.com (100.115.244.119) 56(84) bytes of data. 64 bytes from 100.115.244.119: icmp_seq=1 ttl=59 time=0.911 ms 64 bytes from 100.115.244.119: icmp_seq=2 ttl=59 time=0.850 ms 64 bytes from 100.115.244.119: icmp_seq=3 ttl=59 time=0.814 ms
,
Oct 11 2016
chromeos9-row1-cart1-host8-servo is down.
,
Oct 11 2016
chromeos2-row11-rack1-host4.cros is down. It went down in the middle of a test job I was running. I've scheduled a repair through cautotest/
,
Oct 14 2016
chromeos9-row1-cart2-host2 - Kevin is down.
,
Oct 18 2016
chromeos1-grover-host7 is reset chromeos9-row1-cart2-host2 - Kevin is up now
,
Oct 18 2016
chromeos1-grover-host4 internal battery got reset and able to ping now.
,
Oct 18 2016
chromeos1-grover-host6 got reset and able to ping now.
,
Oct 18 2016
chromeos2-row11-rack5-host4 got reset.
,
Oct 18 2016
chromeos2-row11-rack3-host3 got reset.
,
Oct 18 2016
chromeos2-row11-rack1-host6 got reset
,
Oct 18 2016
chromeos2-row11-rack2-host5 got EC reset.
,
Oct 19 2016
chromeos9-row4-rack8-host3 chromeos9-row4-rack7-host4 chromeos2-row11-rack3-host3 The above hosts got reset and repair mode.
,
Oct 20 2016
chromeos9-row1-cart2-host2-servo is down.
,
Oct 20 2016
chromeos9-row1-cart2-host2-servo is u now. jongkyuj@jongkyuj0:~$ ping chromeos9-row1-cart2-host2-servo PING chromeos9-row1-cart2-host2-servo.cros.corp.google.com (100.115.97.39) 56(84) bytes of data. 64 bytes from 100.115.97.39: icmp_seq=78 ttl=60 time=1.04 ms 64 bytes from 100.115.97.39: icmp_seq=79 ttl=60 time=0.736 ms 64 bytes from 100.115.97.39: icmp_seq=80 ttl=60 time=0.813 ms 64 bytes from 100.115.97.39: icmp_seq=81 ttl=60 time=0.575 ms 64 bytes from 100.115.97.39: icmp_seq=82 ttl=60 time=0.614 ms 64 bytes from 100.115.97.39: icmp_seq=83 ttl=60 time=0.748 ms
,
Oct 20 2016
I am unable to remotely image chromeos2-row11-rack2-host3-router. I have a USB stick with the Panther AP image at my desk - Paul, can you help to reimage the router with the USB stick? You may need to borrow a monitor cart from the team in Atlantis.
,
Oct 26 2016
ping chromeos2-row11-rack4-host5-servo is down PING chromeos2-row11-rack4-host5-servo.cros.corp.google.com (100.115.244.123) 56(84) bytes of data. ^C --- chromeos2-row11-rack4-host5-servo.cros.corp.google.com ping statistics --- 16 packets transmitted, 0 received, 100% packet loss, time 15119ms
,
Oct 26 2016
chromeos2-row11-rack4-host5-servo is up now jongkyuj@jongkyuj0:~$ ping chromeos2-row11-rack4-host5-servo PING chromeos2-row11-rack4-host5-servo.cros.corp.google.com (100.115.244.123) 56(84) bytes of data. 64 bytes from 100.115.244.123: icmp_seq=1 ttl=59 time=0.758 ms 64 bytes from 100.115.244.123: icmp_seq=2 ttl=59 time=0.710 ms 64 bytes from 100.115.244.123: icmp_seq=3 ttl=59 time=0.826 ms
,
Nov 1 2016
Router at chromeos9-row1-cart3-host6-router is not pingable.
,
Nov 1 2016
Router at chromeos9-row1-cart4-host1-router is not pingable.
,
Nov 4 2016
Assigning to aashutoshk@ for now, but donator@ will help in chromeos9 (B1758).
,
Dec 5 2016
This is the only Caroline board in cautotest and it is down: chromeos1-dev-host9 http://cautotest/afe/#tab_id=view_host&object_id=5713
,
Dec 6 2016
chromeos1-dev-host9 is up and running now.
,
Jan 18 2017
Please fix this Caroline host, its the only one we have for wifi_matfunc/wifi_perf: chromeos1-dev-host9 http://cautotest/afe/#tab_id=view_host&object_id=5713
,
Jan 18 2017
Please fix this Chell host: chromeos9-row4-rack1-host4
,
Jan 18 2017
As discussed with Kirtika, removing chromeos1-dev-host9 from cautotest as it is used for adhoc testing and should not run autotest suites. Currently there is an open issue for installing caroline in 1758 https://buganizer.corp.google.com/issues/33432016 The caroline device USB ethernet dongle seems changed and it is resolving to chromeos1-dev-host8 and it is up n running. @80: The chell failure is tracked here https://buganizer.corp.google.com/issues/34393500 All Unpingable devices to be updated @ https://buganizer.corp.google.com/issues/32915204
,
Jan 31 2017
I see a Caroline in autotest that is down and not pingable: chromeos9-row1-cart2-host3 Can we get this fixed? Is this the one in 1758?
,
Jan 31 2017
This Chell is also down: chromeos9-row4-rack1-host4
,
Jan 31 2017
This Elm's router is down: chromeos9-row4-rack6-host3-router.cros
,
Jan 31 2017
This device is also down: chromeos9-row1-cart1-host7.cros
,
Jan 31 2017
chromeos9-row1-cart2-host3 is 1758. I have updated the unpingable devices to the following issue https://buganizer.corp.google.com/issues/34393500
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by jongkyuj@google.com
, Aug 11 2016