> Sorry to hear that happened. Cockpit depends on Network manager to provide it's network functionality. Network manager is pretty standard part of many linux distros. Having the cockpit-networking package depend on it is not a mistake, it needs to be there to ensure that cockpit has what it needs to run.
> I'm not sure how removing cockpit would bork a server though. I've been able to install and uninstall cockpit-networking on lots of systems without issues. Do you have any more details you can provide us? What Version/OS was this on? which commands did you run? A way for us to reproduce the errors you had would be helpful.

It was simple. Dnf remove Cockpit -> removed network manager, which I did not notice for several months. Server reboot -> all DNS related things have suddenly failed.

It was either Fedora server 25, or cloud base 25 images. Essentially anything that ships with Cockpit should have NM "installed first" (marked, etc..) so DNF knows that we actually want it there, regardless of Cockpit. Or whatever other solution that would prevent it be uninstalled while maintaining the rest of the usual functionality of dnf. Changing dnf configuration is not exactly the best solution...


Radka
  

Radka Janeková
.NET & OpenShift Engineer, Red Hat
IRC: radka | Freenode: Rhea


On Tue, Oct 17, 2017 at 3:59 AM, Peter <petervo@redhat.com> wrote:
Sorry to hear that happened. Cockpit depends on Network manager to provide it's network functionality. Network manager is pretty standard part of many linux distros. Having the cockpit-networking package depend on it is not a mistake, it needs to be there to ensure that cockpit has what it needs to run.

I'm not sure how removing cockpit would bork a server though. I've been able to install and uninstall cockpit-networking on lots of systems without issues. Do you have any more details you can provide us? What Version/OS was this on? which commands did you run? A way for us to reproduce the errors you had would be helpful.

On 10/16/2017 06:20 PM, Radka Janekova wrote:
Hi,

so recently I managed to destroy[1] two production servers by removing what I saw as useless web-config utility. Apparently Cockpit depends on NetworkManager, which nobody would expect and is easily overlooked.

PLEASE FIX

[1] https://cloud.rhea-ayase.eu/s/eH6JX43kYErHJ3s

Cheers,
Radka
------------------------------------------------------------------------
*Radka Janeková*
.NET & OpenShift Engineer, Red Hat
*radka.janek@redhat.com <mailto:radka.janek@redhat.com>*
IRC: radka | Freenode: Rhea



_______________________________________________
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpit-devel-leave@lists.fedorahosted.org

_______________________________________________
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpit-devel-leave@lists.fedorahosted.org