ChromeOS version: 64.0.3282.144 (the issue is reported since Oct 2017)
ChromeOS device model: Lenovo N21, N22, and N23 and Asus C200 (everything customer has)
Case#: 15144166

Description:
The Chromebooks are disconnecting from the AP when there is a latency spike reported in the APs, the issue does not affects other devices as android, Mac and windows computers. They are checking this case with Aruba (AP manufacturer) as well, but they are contacting us since the issue only affects chrome devices. 
AP model: Aruba 225 AP

From what I see in logs, this happens way more often than customer sees, constant disconnects, it just might be more evident during latency spikes.


Steps to reproduce: 
1) Connect the Chromebooks to the AP 
2) Wait for a latency spike 


Current Behavior / Reproduction: 
The Chromebooks will disconnect from the AP and will try to connect to another 

Expected Behavior: 
Device stays connected


Drive link to logs: 
Logs from Aruba - 
LR03J7EH dropped its connection at 14:25 today, 3/6/18. https://drive.google.com/file/d/1g7yPXl33PiE32b9_5rCjpsFeKn2iPBGH/view?usp=sharing

LR03J8KT dropped its connection at 14:14 today, 3/6/18. 
https://drive.google.com/file/d/1h_VJL89339DAFz-pG5ky-Hzmf8dmMijX/view?usp=sharing

Debug logs from device - 
https://drive.google.com/file/d/1-m9hUEAgpmIw_8LyD8axt_Y-v_C4HZTB/view?usp=sharing
Disconnections happened on this Chromebook at the following times: 
12:28pm 
12:30pm 
12:40pm 
12:41pm 
12:43pm 
(I assume on March 12).


What I found in logs - 
2018-03-12T12:28:29.808474-05:00 DEBUG wpa_supplicant[667]: RTM_NEWLINK: ifi_index=2 ifname=wlan0 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP])
2018-03-12T12:28:29.826415-05:00 DEBUG wpa_supplicant[667]: nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
2018-03-12T12:28:29.826440-05:00 DEBUG wpa_supplicant[667]: nl80211: Delete station 18:64:72:28:6d:70
2018-03-12T12:28:29.829952-05:00 DEBUG wpa_supplicant[667]: nl80211: Drv Event 39 (NL80211_CMD_DEAUTHENTICATE) received for wlan0
2018-03-12T12:28:29.829971-05:00 DEBUG wpa_supplicant[667]: nl80211: Deauthenticate event
2018-03-12T12:28:29.829987-05:00 DEBUG wpa_supplicant[667]: wlan0: Event DEAUTH (12) received
2018-03-12T12:28:29.830000-05:00 DEBUG wpa_supplicant[667]: wlan0: Deauthentication notification
2018-03-12T12:28:29.830012-05:00 DEBUG wpa_supplicant[667]: wlan0:  * reason 4 (locally generated)
2018-03-12T12:28:29.830026-05:00 DEBUG wpa_supplicant[667]: wlan0:  * address 18:64:72:28:6d:70
2018-03-12T12:28:29.830038-05:00 DEBUG wpa_supplicant[667]: Deauthentication frame IE(s) - hexdump(len=0): [NULL]
2018-03-12T12:28:29.830054-05:00 NOTICE wpa_supplicant[667]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:64:72:28:6d:70 reason=4 locally_generated=1

Similar events happen every time they have a disconnect and actually way more often than customer reported and than it would appear to make any sense.