> The problem persists if you upgrade from 16.04.3 directly to 17.04 ( as described https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/comments/23 )
I can confirm this. My upgrade path was xenial -> zesty -> artful and I had to run "touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf" so network-manager could handle my enp2s0 device.
> The problem persists if you upgrade from 16.04.3 directly to 17.04 ( as described https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/1658921/ comments/ 23 )
I can confirm this. My upgrade path was xenial -> zesty -> artful and I had to run "touch /etc/NetworkMan ager/conf. d/10-globally- managed- devices. conf" so network-manager could handle my enp2s0 device.