New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 645670 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Email to this user bounced
Closed: Sep 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[chaos]Install 4 more whirlwind pcaps in chaos

Project Member Reported by bmahadev@chromium.org, Sep 9 2016

Issue description

Right now we have just 4 packet capturers. It would be good to increase the count to atleast as much as we had before, which is about 8. Since the lab has many unused OTA whirlwinds, lets use them top add more packet_capture to chaos lab.

1. Install device in chaos
2. Add to cauto with labels : variant:whirlwind, board:whirlwind, packet_capture, chaos_chamber, phase:EVT, pool:wifichaos, sku:whirlwind_cpu_qualcomm_1Gb

 

Comment 1 by jongkyuj@google.com, Sep 12 2016

Status: Started (was: Assigned)
1. Install device in chaos Done
Install 4 Whirlwinds to following hosts and replaced them from Stumpys:
chromeos3-row1-rack2-host7
chromeos3-row1-rack2-host8
chromeos3-row1-rack2-host11
chromeos3-row1-rack2-host12

Comment 2 by jongkyuj@google.com, Sep 12 2016

Status: Fixed (was: Started)
Add to cauto with labels : variant:whirlwind, board:whirlwind, packet_capture, chaos_chamber, phase:EVT, pool:wifichaos, sku:whirlwind_cpu_qualcomm_1Gb Done
Added labels for below hosts:
chromeos3-row1-rack2-host7
chromeos3-row1-rack2-host8
chromeos3-row1-rack2-host11
chromeos3-row1-rack2-host12

Comment 3 by jongkyuj@google.com, Sep 12 2016

Status: Verified (was: Fixed)
jongkyuj@jongkyuj0:~$ ping chromeos3-row1-rack2-host7
PING chromeos3-row1-rack2-host7.cros.corp.google.com (172.22.38.53) 56(84) bytes of data.
64 bytes from 172.22.38.53: icmp_seq=1 ttl=62 time=0.751 ms
64 bytes from 172.22.38.53: icmp_seq=2 ttl=62 time=0.732 ms
64 bytes from 172.22.38.53: icmp_seq=3 ttl=62 time=0.621 ms
^C
--- chromeos3-row1-rack2-host7.cros.corp.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 0.621/0.701/0.751/0.061 ms
jongkyuj@jongkyuj0:~$ ping chromeos3-row1-rack2-host8
PING chromeos3-row1-rack2-host8.cros.corp.google.com (172.22.38.54) 56(84) bytes of data.
64 bytes from 172.22.38.54: icmp_seq=1 ttl=62 time=0.628 ms
64 bytes from 172.22.38.54: icmp_seq=2 ttl=62 time=0.757 ms
64 bytes from 172.22.38.54: icmp_seq=3 ttl=62 time=0.839 ms
64 bytes from 172.22.38.54: icmp_seq=4 ttl=62 time=0.591 ms
^C
--- chromeos3-row1-rack2-host8.cros.corp.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 0.591/0.703/0.839/0.104 ms
jongkyuj@jongkyuj0:~$ ping chromeos3-row1-rack2-host11
PING chromeos3-row1-rack2-host11.cros.corp.google.com (172.22.38.57) 56(84) bytes of data.
64 bytes from 172.22.38.57: icmp_seq=1 ttl=62 time=0.693 ms
64 bytes from 172.22.38.57: icmp_seq=2 ttl=62 time=0.728 ms
64 bytes from 172.22.38.57: icmp_seq=3 ttl=62 time=0.596 ms
64 bytes from 172.22.38.57: icmp_seq=4 ttl=62 time=0.718 ms
^C
--- chromeos3-row1-rack2-host11.cros.corp.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 0.596/0.683/0.728/0.061 ms
jongkyuj@jongkyuj0:~$ ping chromeos3-row1-rack2-host12
PING chromeos3-row1-rack2-host12.cros.corp.google.com (172.22.38.58) 56(84) bytes of data.
64 bytes from 172.22.38.58: icmp_seq=1 ttl=62 time=0.774 ms
64 bytes from 172.22.38.58: icmp_seq=2 ttl=62 time=0.578 ms
64 bytes from 172.22.38.58: icmp_seq=3 ttl=62 time=0.479 ms
Can you also please add one of the stumpies for debugging purposes ? but leave it in locked state so that test don't pick up stumpy.

Comment 5 by jongkyuj@google.com, Sep 12 2016

Installed stumpy pcap on following host and host is locked:
chromeos3-row1-rack2-host15

jongkyuj@jongkyuj0:~$ ping chromeos3-row1-rack2-host15
PING chromeos3-row1-rack2-host15.cros.corp.google.com (172.22.38.61) 56(84) bytes of data.
64 bytes from 172.22.38.61: icmp_seq=1 ttl=62 time=0.654 ms
64 bytes from 172.22.38.61: icmp_seq=2 ttl=62 time=0.572 ms
64 bytes from 172.22.38.61: icmp_seq=3 ttl=62 time=1.10 ms

Comment 6 by jongkyuj@google.com, Sep 12 2016

The following labels are added for stumpy:
variant:stempy, board:stumpy, packet_capture, chaos_chamber, phase:EVT, pool:wifichaos
Cauto show it is Platform veyron_mighty. Please check if some existing device already uses this hostname. If it is a free slot, you need to delete this host and re-add host into cauto.

Comment 8 by jongkyuj@google.com, Sep 14 2016

Added the Stumpy to chromeos3-row1-rack2-host14 and added the labels.
jongkyuj@jongkyuj0:~/chromiumos/src/third_party/autotest/files/cli$ ping chromeos3-row1-rack2-host14
PING chromeos3-row1-rack2-host14.cros.corp.google.com (172.22.38.60) 56(84) bytes of data.
64 bytes from 172.22.38.60: icmp_seq=1 ttl=62 time=0.660 ms
64 bytes from 172.22.38.60: icmp_seq=2 ttl=62 time=0.693 ms
64 bytes from 172.22.38.60: icmp_seq=3 ttl=62 time=0.673 ms
64 bytes from 172.22.38.60: icmp_seq=4 ttl=62 time=0.644 ms
Status: Assigned (was: Verified)
These devices are showing up as stumpy and not whirlwind. You added whirlwind devices right not stumpies ?

chromeos3-row1-rack2-host7
chromeos3-row1-rack2-host8
chromeos3-row1-rack2-host11
chromeos3-row1-rack2-host12
chromeos3-row1-rack2-host7
chromeos3-row1-rack2-host8
chromeos3-row1-rack2-host11
chromeos3-row1-rack2-host12

Removed the platform "stumpy" and added new platform "storm" for above hosts.

Status: Fixed (was: Assigned)
The platform has been changed with "storm".

Status: Verified (was: Fixed)

Sign in to add a comment