Unfortunately the report seems to have been filed long enough after the errors that the the details are not in the network event log (which is a limited size circular buffer).

+cernekee@ in case there is something interesting in the shill section.

I'm on my way to SFO now so I'll see how a Pixel running 67 does anyway.

I didn't have any issues connecting (in fact everything went quite smoothly). Assigning to cernekee@ to take a look at the Shill side of things and investigate or resolve.

I'll be back in SFO on Friday afternoon and can try again. I really thought I submitted moments after the failed connection, but I guess these things progress quickly. I can also close everything else next time so that the netlog doesn't get overrun.

Anything else I should keep in mind?

The best way to report this is shortly after rebooting, then we only have a
relatively short log to look at. On the other hand this may only occur when
the device has not been rebooted recently, so if you notice the bug file a
report immediately, then reboot and try to repro and file another report if
you can.

Thanks!

Signal levels are mostly very low:

2018-04-02T07:17:39.267786-07:00 DEBUG wpa_supplicant[650]: wlan0: 132: f0:29:29:00:00:0f ssid='1' wpa_ie_len=0 rsn_ie_len=0 caps=0x1101 level=-86 freq=5500 
2018-04-02T07:17:39.267792-07:00 DEBUG wpa_supplicant[650]: wlan0:    allow in non-WPA/WPA2
2018-04-02T07:17:39.267801-07:00 DEBUG wpa_supplicant[650]: wlan0:    selected BSS f0:29:29:00:00:0f ssid='1'
[...]
2018-04-02T07:17:39.267948-07:00 NOTICE wpa_supplicant[650]: wlan0: SME: Trying to authenticate with f0:29:29:00:00:0f (SSID='1' freq=5500 MHz)
[...]
2018-04-02T07:17:39.595171-07:00 DEBUG wpa_supplicant[650]: wlan0: Event ASSOC_TIMED_OUT (15) received
2018-04-02T07:17:39.595182-07:00 DEBUG wpa_supplicant[650]: wlan0: SME: Association timed out
2018-04-02T07:17:39.595190-07:00 DEBUG wpa_supplicant[650]: wlan0: Radio work 'sme-connect'@0x59953711b040 done in 0.327305 seconds
2018-04-02T07:17:39.595195-07:00 DEBUG wpa_supplicant[650]: wlan0: radio_work_free('sme-connect'@0x59953711b040: num_active_works --> 0
2018-04-02T07:17:39.595202-07:00 DEBUG wpa_supplicant[650]: Added BSSID f0:29:29:00:00:0f into blacklist


2018-04-02T07:17:38.118704-07:00 DEBUG wpa_supplicant[650]: wlan0: 129: 70:10:5c:00:00:0c ssid='1' wpa_ie_len=0 rsn_ie_len=0 caps=0x1421 level=-81 freq=2437 
2018-04-02T07:17:38.118714-07:00 DEBUG wpa_supplicant[650]: wlan0:    allow in non-WPA/WPA2
2018-04-02T07:17:38.118725-07:00 DEBUG wpa_supplicant[650]: wlan0:    selected BSS 70:10:5c:00:00:0c ssid='1'
[...]
2018-04-02T07:17:38.119378-07:00 NOTICE wpa_supplicant[650]: wlan0: SME: Trying to authenticate with 70:10:5c:00:00:0c (SSID='1' freq=2437 MHz)
[...]
2018-04-02T07:17:38.469903-07:00 DEBUG wpa_supplicant[650]: wlan0: Event ASSOC_TIMED_OUT (15) received
2018-04-02T07:17:38.469916-07:00 DEBUG wpa_supplicant[650]: wlan0: SME: Association timed out
2018-04-02T07:17:38.469928-07:00 DEBUG wpa_supplicant[650]: wlan0: Radio work 'sme-connect'@0x599537118430 done in 0.350644 seconds
2018-04-02T07:17:38.469936-07:00 DEBUG wpa_supplicant[650]: wlan0: radio_work_free('sme-connect'@0x599537118430: num_active_works --> 0
2018-04-02T07:17:38.469945-07:00 DEBUG wpa_supplicant[650]: Added BSSID 70:10:5c:00:00:0c into blacklist


2018-04-02T07:17:36.881986-07:00 DEBUG wpa_supplicant[650]: wlan0: 122: f0:29:29:00:00:0d ssid='1' wpa_ie_len=0 rsn_ie_len=0 caps=0x1101 level=-82 freq=5540 
2018-04-02T07:17:36.881994-07:00 DEBUG wpa_supplicant[650]: wlan0:    allow in non-WPA/WPA2
2018-04-02T07:17:36.882005-07:00 DEBUG wpa_supplicant[650]: wlan0:    selected BSS f0:29:29:00:00:0d ssid='1'
[...]
2018-04-02T07:17:36.882182-07:00 NOTICE wpa_supplicant[650]: wlan0: SME: Trying to authenticate with f0:29:29:00:00:0d (SSID='1' freq=5540 MHz)


2018-04-02T07:17:35.402209-07:00 DEBUG wpa_supplicant[650]: wlan0: 120: f4:0f:1b:00:00:0b ssid='1' wpa_ie_len=0 rsn_ie_len=0 caps=0x1421 level=-73 freq=2437 
2018-04-02T07:17:35.402213-07:00 DEBUG wpa_supplicant[650]: wlan0:    allow in non-WPA/WPA2
2018-04-02T07:17:35.402220-07:00 DEBUG wpa_supplicant[650]: wlan0:    selected BSS f4:0f:1b:00:00:0b ssid='1'
[...]
2018-04-02T07:17:35.402329-07:00 NOTICE wpa_supplicant[650]: wlan0: SME: Trying to authenticate with f4:0f:1b:00:00:0b (SSID='1' freq=2437 MHz)


2018-04-02T07:17:33.930904-07:00 DEBUG wpa_supplicant[650]: wlan0: 116: f4:0f:1b:00:00:0a ssid='1' wpa_ie_len=0 rsn_ie_len=0 caps=0x1101 level=-82 freq=5580 
2018-04-02T07:17:33.930912-07:00 DEBUG wpa_supplicant[650]: wlan0:    allow in non-WPA/WPA2
2018-04-02T07:17:33.930924-07:00 DEBUG wpa_supplicant[650]: wlan0:    selected BSS f4:0f:1b:00:00:0a ssid='1'
[...]
2018-04-02T07:17:33.931322-07:00 NOTICE wpa_supplicant[650]: wlan0: SME: Trying to authenticate with f4:0f:1b:00:00:0a (SSID='1' freq=5580 MHz)


The strongest AP in the list (all SSIDs, not just yours) is at -63.  Around the office I see a bunch of APs in the -40s and -50s, with some local ones in the -30s.  So -63 dBm as the high water mark seems low.

It might be worth comparing the "New scan results" section of file:///var/log/net.log with another Chromebook in the same location, to isolate whether it's a poor RF environment overall or if there is something particular to this unit that is hurting RF performance.

I also have to wonder wpa_supplicant knows to reset the AP blacklist if the signal level changes drastically (indicating that the Chromebook may have been moved out of a dead zone)?

I tried again and successfully connected at SFO, though I've had issues with this device and SFO in the past. Will return to this bug if it happens again - I travel somewhat frequently :)