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

Issue 601659 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner:
Last visit 15 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[matfunc] network_WiFi_SimpleConnect.wifi_checkWPA2_CCMP_PMF fails on Whirlwind

Project Member Reported by tienchang@chromium.org, Apr 8 2016

Issue description

Looking at wmatrix and a run on chell, only the devices with Whirlwind have been failing this test with "hostapd failed to initialize AP interface."
https://wmatrix.googleplex.com/failures/wifi_matfunc?tests=network_WiFi_SimpleConnect.wifi_checkWPA2_CCMP_PMF

DUTs with Whirlwind APs:
Ultima
Chell
Sentry*
Edgar
Setzer
Terra
Lars*
Gandof

DUTs failing this test for the noted reason:
Ultima
Chell
Edgar
Setzer
Terra
Gandof
Celes*

Only those starred aren't in both categories, so maybe it's an Intel Stonepeak bug, but the traceback doesn't make me think that.

Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 804, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 461, in execute
    dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 376, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/server/site_tests/network_WiFi_SimpleConnect/network_WiFi_SimpleConnect.py", line 36, in run_once
    self.context.configure(router_conf)
  File "/usr/local/autotest/server/cros/network/wifi_test_context_manager.py", line 164, in configure
    multi_interface=multi_interface)
  File "/usr/local/autotest/server/site_linux_router.py", line 436, in hostap_configure
    self.start_hostapd(configuration)
  File "/usr/local/autotest/server/site_linux_router.py", line 307, in start_hostapd
    raise error.TestFail('hostapd failed to initialize AP '
TestFail: hostapd failed to initialize AP interface.

Sample log from Setzer:
https://http://ubercautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/59177868-chromeos-test/android1758-row4-rack2-host4/network_WiFi_SimpleConnect.wifi_checkWPA2_CCMP_PMF

Assigning to quiche@ but do make the right reassignment if needed!
 

Comment 1 by pstew@chromium.org, Apr 8 2016

Owner: ejcaruso@chromium.org
This might be related to the wpa_supplicant upgrade.
Cc: grundler@chromium.org
wpa_supplicant seems to be acting as expected from the logs, so I'm not sure what could be the problem here. If it's hostap side, maybe Grant might know something.

Comment 3 by grundler@google.com, Apr 11 2016

Has this been failing since March 11 builds? If so, then I'd suspect wpa_supplicant "upgrade".

hostapd will only affect Wifi management for devices talking to whirlwind/Arkham APs...again, that doesn't seem consistent.

That back trace isn't enough info and link didn't work as-is:
    https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/59177868-chromeos-test/android1758-row4-rack2-host4/debug/?pli=1

I can look at this a bit in the afternoon, but I am pretty sure I need a bit more help with triaging this a bit deeper.
Ah yes, it looks like this test began failing with this particular failure message since March 11.

(Ctrl+F and backwards check for the last instance of "hostapd failed to initialize")
https://wmatrix.googleplex.com/failures/wifi_matfunc?tests=network_WiFi_SimpleConnect.wifi_checkWPA2_CCMP_PMF&days_back=45&releases=51

Comment 5 by quiche@chromium.org, Apr 11 2016

I think PMF has always failed on the whirlwind testbed ap image. The problem is that the driver/firmware on the AP image doesn't support PMF. But we can't update to a kernel that does, because newer kernels cause regressions on other tests.

See bug 504534.
Mergedinto: 504534
Status: Duplicate (was: Assigned)

Sign in to add a comment