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

Issue 792752 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 785615



Sign in to add a comment

CHAOS LAB: network_WiFi_ChaosConnectDisconnect fails against Asus AP rt n56u at chromeos3-row3-rack1-host5

Project Member Reported by harpreet@chromium.org, Dec 7 2017

Issue description

chromeos3-row3-rack1-host5
rt n56u
AsusAPConfigurator


Router configured


Test failed due to command execution error (line 41 in test script)


 Unhandled AutoservRunError: command execution error
  * Command:
      /usr/bin/ssh -a -x  -o ControlPath=/tmp/_autotmp_OERoD0ssh-master/socket
      -o StrictHostKeyChecking=no -o UserKnownHostsFile=/tmp/tmpLaxQAX -o
      BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=300 -o
      ServerAliveCountMax=3 -o ConnectionAttempts=1 -l root -p 22
      chromeos3-row1-rack1-host1.cros " if type \"logger\" > /dev/null 2>&1;
      then logger -tag \"autotest\" \"server[stack::get_wlanif|_get_wlanif|run]
      -> ssh_run(/bin/ip link set dev monitor1 down)\";fi; /bin/ip link set dev
      monitor1 down"
  Exit status: 1
  Duration: 0.0246579647064

  stderr:
  Cannot find device "monitor1"
  Traceback (most recent call last):
    File "/mnt/host/source/src/third_party/autotest/files/client/common_lib/test.py", line 831, in _call_test_function
      return func(*args, **dargs)
    File "/mnt/host/source/src/third_party/autotest/files/client/common_lib/test.py", line 495, in execute
      dargs)
    File "/mnt/host/source/src/third_party/autotest/files/client/common_lib/test.py", line 362, in _call_run_once_with_retry
      postprocess_profiled_run, args, dargs)
    File "/mnt/host/source/src/third_party/autotest/files/client/common_lib/test.py", line 400, in _call_run_once
      self.run_once(*args, **dargs)
    File "/mnt/host/source/src/third_party/autotest/files/server/site_tests/network_WiFi_ChaosConnectDisconnect/network_WiFi_ChaosConnectDisconnect.py", line 41, in run_once
      capturer.start_capture(capturer_frequency, ht_type=capturer_ht_type)
    File "/mnt/host/source/src/third_party/autotest/files/server/site_linux_system.py", line 317, in start_capture
      self._capture_interface = self.get_wlanif(frequency, 'monitor')
    File "/mnt/host/source/src/third_party/autotest/files/server/site_linux_system.py", line 538, in get_wlanif
      phytype, spatial_streams, frequency, same_phy_as)
    File "/mnt/host/source/src/third_party/autotest/files/server/site_linux_system.py", line 475, in _get_wlanif
      self.cmd_ip, net_dev.if_name))
    File "/mnt/host/source/src/third_party/autotest/files/server/hosts/ssh_host.py", line 323, in run
      return self.run_very_slowly(*args, **kwargs)
    File "/mnt/host/source/src/third_party/autotest/files/server/hosts/ssh_host.py", line 312, in run_very_slowly
      ssh_failure_retry_ok)
    File "/mnt/host/source/src/third_party/autotest/files/server/hosts/ssh_host.py", line 262, in _run
      raise error.AutoservRunError("command execution error", result)
  AutoservRunError: command execution error
  * Command:
      /usr/bin/ssh -a -x  -o ControlPath=/tmp/_autotmp_OERoD0ssh-master/socket
      -o StrictHostKeyChecking=no -o UserKnownHostsFile=/tmp/tmpLaxQAX -o
      BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=300 -o
      ServerAliveCountMax=3 -o ConnectionAttempts=1 -l root -p 22
      chromeos3-row1-rack1-host1.cros " if type \"logger\" > /dev/null 2>&1;
      then logger -tag \"autotest\" \"server[stack::get_wlanif|_get_wlanif|run]
      -> ssh_run(/bin/ip link set dev monitor1 down)\";fi; /bin/ip link set dev
      monitor1 down"
  Exit status: 1
  Duration: 0.0246579647064

  stderr:
  Cannot find device "monitor1"

 
Summary: CHAOS LAB: network_WiFi_ChaosConnectDisconnect fails against Asus AP rt n56u at chromeos3-row3-rack1-host5 (was: network_WiFi_ChaosConnectDisconnect fails against Asus AP rt n56u at chromeos3-row3-rack1-host5)
Cc: rjahagir@chromium.org
Status: WontFix (was: Assigned)
Closing all Choas lab bugs as we are moving away from dynamic configuration of the APs. These APs have all been reset and FW updated as needed. We have also split the APs equally across 3 RF chambers where they will be manually configured (1 time) to specified configurations. 

Sign in to add a comment