The following revision refers to this bug:
  https://chromium.googlesource.com/aosp/platform/system/connectivity/shill/+/38618ae30e6f5c19a7d6287a0de1210c4a0ffd33

commit 38618ae30e6f5c19a7d6287a0de1210c4a0ffd33
Author: Kevin Cernekee <cernekee@google.com>
Date: Wed Jun 01 22:00:40 2016

openvpn: Handle reconnections the same way as ThirdPartyVpnDriver

Use the new APIs and callbacks to clean up the way OpenVPN handles
link up/down/change events.  This fixes a couple of UI anomalies seen
when using OpenVPN.

BUG= chromium:616573 
TEST=`FEATURES=test emerge-link shill`
TEST=connect to openvpn server and add/remove network connections

Change-Id: I2adf24f6d645ebf5070697b9324da03de4a4d237
Reviewed-on: https://chromium-review.googlesource.com/348801
Commit-Ready: Kevin Cernekee <cernekee@chromium.org>
Tested-by: Kevin Cernekee <cernekee@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Kirtika Ruchandani <kirtika@google.com>

[modify] https://crrev.com/38618ae30e6f5c19a7d6287a0de1210c4a0ffd33/mock_virtual_device.h
[modify] https://crrev.com/38618ae30e6f5c19a7d6287a0de1210c4a0ffd33/vpn/openvpn_driver.h
[modify] https://crrev.com/38618ae30e6f5c19a7d6287a0de1210c4a0ffd33/vpn/openvpn_driver.cc
[modify] https://crrev.com/38618ae30e6f5c19a7d6287a0de1210c4a0ffd33/vpn/openvpn_driver_unittest.cc

The chrome://settings page does not auto-refresh to reflect to correct connection status

Steps to repro:
1) connect to openvpn or any other vpn service.
2) Once connected, Click the dropdown menu and select preferred network.
3) Remove the connected service (in this case openvpn)

Expected Result: Chrome://settings and bottom tray should show updated service status.

Actual Result: Chrome://settings page does not auto-refresh to show the updated status. 

Workaround: Manually refreshing the page fixes it.
I am guessing this change may have caused a regression, if not I can open a new issue. 

Tested: Cyan-cheets 8530.5.0. logs@ 
https://cloud.google.com/console/storage/chromiumos-test-logs/bugfiles/cr/616573/

I think the lack of refresh on the chrome://settings VPN status is a KI, which will be addressed when the Settings page is rewritten?

https://code.google.com/p/chrome-os-partner/issues/detail?id=52303

Correct. If the problem persists in chrome://md-settings, we should file a new bug against that UI.

Either way we shouldn't re-open a fixed bug for a fairly different symptom.

Just to clarify: this bug is for the tray/notifications associated with OpenVPN reconnections, not the chrome://settings behavior.  It is possible that the CL that fixed this issue had unwanted side effects, so it is good that Aashutosh was looking out for possible regressions.

I don't even see VPN settings in chrome://md-settings (my build is about 1 week old).

We don't have an "Add Network" section yet when no VPN is configured. If a
VPN is configured it should be showing up .