Bug 1494521

Summary: cockpit is not started on deployed hosts
Product: [oVirt] ovirt-host-deploy Reporter: Sandro Bonazzola <sbonazzo>
Component: CoreAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED CURRENTRELEASE QA Contact: Pavol Brilla <pbrilla>
Severity: medium Docs Contact:
Priority: medium    
Version: masterCC: bugs, didi, lsvaty, nicolas
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: 1.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-12 12:57:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1478904    

Description Sandro Bonazzola 2017-09-22 12:14:35 UTC
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

Comment 1 Pavol Brilla 2018-01-09 12:44:00 UTC
# 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

Comment 2 Yedidyah Bar David 2019-05-20 08:38:08 UTC
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.

Comment 3 Sandro Bonazzola 2019-05-21 06:43:25 UTC
(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.

Comment 4 Yedidyah Bar David 2019-05-21 06:51:16 UTC
Filed bug 1712242.