Another workaround is to reconnect the ethernet cable: network-manager will then reconnect (new DHCP request).
Is it possible that this bug is related to the fact that network is established by ifupdown package (as it is simple DHCP/auto config) and then network-manager does not properly detect that interface is already up (or some kind of timing issue when eth0 is still getting IP from DHCP server when n-m is checking it).
Another workaround is to reconnect the ethernet cable: network-manager will then reconnect (new DHCP request).
Is it possible that this bug is related to the fact that network is established by ifupdown package (as it is simple DHCP/auto config) and then network-manager does not properly detect that interface is already up (or some kind of timing issue when eth0 is still getting IP from DHCP server when n-m is checking it).