On Tue, Oct 17, 2017 at 10:17 AM Radka Janekova <radka.janek(a)redhat.com>
> That being said, elsewhere in the thread it was reported that
original poster was using Cloud Edition, not Server Edition. This
environment group does NOT pull in NetworkManager or Cockpit by default. So
if Cockpit was installed manually it would have pulled NM in as a
dependency solely of Cockpit.
The case I posted is digital ocean standard fedora, and it comes with
cockpit (or did back then...) Even if it was manually installed, shouldn't
it revert configuration back when it's uninstalled? It left behind a
/etc/resolv.conf simlink to nonexistent NetworkManager file.
Hmm, I wonder if this might actually be a bug in the way that Digital Ocean
creates those images, then. It definitely adds Cockpit above and beyond
what we normally ship in the cloud image. So probably their image-creation
script should be updated to mark NetworkManager appropriately, if it's
going to end up actually using it. That's not really something we have
control over though.