Description of problem: cockpit is not started on deployed hosts so when you try to use the "Host Console" button in the Web Admin interface you hit a connection failure accessing port 9090 on the destination host. Version-Release number of selected component (if applicable): ovirt-host-deploy-1.7.0-0.0.master.20170912090102.git1eeb5a2.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. be sure to select iptables cluster since firewalld clusters have separate issues. 2. deploy an host starting from centos minimal 3. try to use "host console" Actual results: host console is unreachable and on host: # service cockpit status Redirecting to /bin/systemctl status cockpit.service ● cockpit.service - Cockpit Web Service Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:cockpit-ws(8) Expected results: host console should be reachable
# yum list ovirt-host-deploy Loaded plugins: product-id, search-disabled-repos, versionlock Installed Packages ovirt-host-deploy.noarch 1.7.0-1.el7ev @rhv-4.2-beta connection to host cockpit after add host works
Now noticed that this does not work after reboot. Perhaps it worked at the time and cockpit's systemd structure/conf change since. We start and enable cockpit.service , but it requires cockpit.socket , and we do not enable this one. So after deploy, I can connect using cockpit, but after reboot, I get: systemctl -a | grep cockpit (empty) systemctl list-unit-files | grep cockpit cockpit-motd.service static cockpit.service static cockpit.socket disabled If I then start cockpit.service, I get: systemctl -a | grep cockpit cockpit-motd.service loaded inactive dead Cockpit motd updater service cockpit.service loaded active running Cockpit Web Service cockpit.socket loaded active running Cockpit Web Service Socket But: # systemctl list-unit-files | grep cockpi cockpit-motd.service static cockpit.service static cockpit.socket disabled Bottom line: Seems like we need to enable (also?) cockpit.socket.
(In reply to Yedidyah Bar David from comment #2) > Bottom line: Seems like we need to enable (also?) cockpit.socket. Please open a new BZ for this, let's fix it in 4.3.5.
Filed bug 1712242.