Hello Team, do we have any updates on this issue? 

Alex, Marcus,

Is this the expected behavior as explained in 
https://bugs.chromium.org/p/chromium/issues/detail?id=559656#c20

for the Chrome OS device Wifi prioritization? 
in M68: (service 3)

2018-11-06T09:20:09.832823-08:00 INFO shill[975]: [INFO:service.cc(290)] wifi service 3 constructed.
2018-11-06T09:20:09.832937-08:00 INFO shill[975]: [INFO:wifi_service.cc(184)] Constructed WiFi service 3 name: [SSID=HIS_FAVORITE_WIFI]
2018-11-06T09:22:33.974797-08:00 INFO shill[975]: [INFO:service.cc(1470)] Service 3: AutoConnect=0->1

in M69/M70 (service 11)
2018-11-05T13:34:27.770369-08:00 INFO shill[1091]: [INFO:service.cc(291)] wifi service 11 constructed.
2018-11-05T13:34:27.770432-08:00 INFO shill[1091]: [INFO:wifi_service.cc(184)] Constructed WiFi service 11 name: [SSID=HIS_FAVORITE_WIFI]
2018-11-05T13:34:27.770561-08:00 INFO shill[1091]: [INFO:service.cc(1474)] Service 11: AutoConnect=0->1

This is unrelated to 559656 for several reasons:
1) 559656 is fixed with M70
2) 559656 actually prefers wifi over ethernet (but connect's to both)
3) 559656 doesn't change the autoconnect behavior

+kirtika for wpa_supplicant expertise

+aghuie who covers networking topics from the PM side

I took a look at the discussion in 559656 and I agree that it should auto connect to the network pushed down via user policy vs any configured network during enrollment (5th prioritization sorting order)

It doesn't look like changes in 559656 would impact that but can someone explain to me what we did change for 69/70? In case we are missing something else that might be configured for the customer's network that affected prioritization.

Was the device connected to another network when it should have auto-connected to the policy network (i.e. swap network) or was it unconnected and should create a new connection?

Yes, it was connected. Prior to 69+ the behavior is that device was connected to another network that was defined via device policy. On login with account on Chromebook that has user defined network policy the  network would switch ( swap network).  

Just an FYI, Reading through other bug reports seems to be the same issue as reported https://bugs.chromium.org/p/chromium/issues/detail?id=559656#c26 and https://bugs.chromium.org/p/chromium/issues/detail?id=904837 . 

In the feedback report from M-70, I can see two services with managed credentials:

/service/1:
SSID: <A>
ManagedCredentials: true
Profile: default (shared)

/service/7
SSID: <B>
ManagedCredentials: true
Profile: chronos (user)

There's no HasEverConnected but that seems to be because this is generated using a GetProperties dbus call, and HasEverConnected is not in the "PropertyStore". Steven/Alex, would it make sense to add it there for diagnostics purposes at least?

Anyways, net.log shows:
2018-11-05T11:16:54.678802-08:00 INFO shill[1086]: [INFO:service.cc(305)] Suppressed autoconnect to service 7 (no endpoints)
2018-11-05T11:16:58.781127-08:00 INFO shill[1086]: [INFO:wifi_service.cc(798)] Rep ep updated for 7. [SSID=....], bssid: ...., sig: -50, sec: rsn, freq: 5260
(nothing interesting)


In the M-68 log (where it works), the same service is under /service/6, and there's a similar message in net.log, but then it follows with:
2018-11-02T12:56:12.712992-07:00 INFO shill[1084]: [INFO:service.cc(312)] Suppressed autoconnect to service 6 (no endpoints)

2018-11-02T12:56:12.713666-07:00 INFO shill[1084]: [INFO:wifi_service.cc(798)] Rep ep updated for 6. [SSID=....], bssid: ...., sig: -49, sec: rsn, freq: 5180
2018-11-02T12:56:12.816417-07:00 INFO shill[1084]: [INFO:service.cc(319)] Connect to service 6: ConnectToBestServicesTask

This is missing from the M-69 log.
I'll try to see what triggers this usually.

I thought this was a duplicate of 904837 as well, isn't it?
Does the auto-connect problem get fixed once you have manually connected to the user policy network?

I was on leave, sorry for the delay.

Does this still repro? If yes, could we get the chrome://policy export?
Thanks!