Description of problem: See bug 1494521, especially bug 1494521 comment 2. Probably a recent change in cockpit's systemd configuration made it require enabling (perhaps also?) cockpit.socket, to make it active after reboots. Version-Release number of selected component (if applicable): Current master, probably since somewhere between 4.2.0 and now How reproducible: Always Steps to Reproduce: 1. Deploy a host 2. Move it to maintenance and reboot 3. Actual results: cockpit is unavailable Expected results: cockpit is available Additional info: bug 1494521 comment 2
*** This bug has been marked as a duplicate of bug 1704282 ***