Description of problem: ovirt-host should enable cockpit by default Version-Release number of selected component (if applicable): cockpit-ovirt-dashboard-0.11.9-0.1.el7ev.noarch ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch Red Hat Enterprise Linux Server release 7.4 (Maipo) How reproducible: 100% Steps to Reproduce: 1.On cleanly reprovisioned RHEL7.4, install ovirt-hosted-engine-setup. 2.Check for cockpit service, it appears off, while should be enabled and running, just like it is on RHEVH-NGN. Actual results: Customer have to manually enable cockpit service. Expected results: Cockpit service should be automatically enabled and started after hosted-engine installed on RHEL based host, just like its happening on RHEVH-NGN hosts. Additional info:
Pavol, this has been fixed and verified working in 4.2.0 with bug #1494521. Can you please try to reproduce with 4.2.1 and attach deployment logs?
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
I think I looked at this bug some time ago, didn't fully understand, and then didn't add any comment :-( The bug is on ovirt-host-deploy, the description says "ovirt-host should enable cockpit by default", but the steps say "On cleanly reprovisioned RHEL7.4, install ovirt-hosted-engine-setup.". I am pretty certain now that the intent is to fix the flow in the "steps" - that is, on the installation of the first hosted-engine host. ovirt-host-deploy already fixed this bug, as Sandro mentioned above, but that's not helpful for the requested flow (which is before ovirt-host-deploy runs). Although it might be solved (if at all) either in ovirt-host or ovirt-hosted-engine-setup, I think the latter makes more sense to me, thus moving there. Also noting that it might make sense to make this a platform bug - to require that EL (any, or some common subset or whatever) will always install/configure/enable/open/etc cockpit.
Not sure that enabling a service and opening firewall ports simply getting an rpm installed as a dependency is a good idea, I'd suggest to move to doc.
(In reply to Simone Tiraboschi from comment #4) > Not sure that enabling a service and opening firewall ports simply getting > an rpm installed as a dependency is a good idea, I'd suggest to move to doc. I agree. We can somehow simplify the process by providing an ansible role for configuring a host to be ready to deploy hosted engine through cockpit, enabling the services and opening the firewall ports. Maybe infra team already did something in this area. Martin?
Added PR on the ovirt upstream site: https://github.com/oVirt/ovirt-site/pull/1536
Cockpit installation had been covered in in for 4.1: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/installation_guide/installing_cockpit_on_linux_hosts For 4.2: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html/installation_guide/installing_cockpit_on_linux_hosts For Ovirt: and https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/installation_guide/installing_cockpit_on_linux_hosts Moving to verified.
(In reply to Sandro Bonazzola from comment #5) > (In reply to Simone Tiraboschi from comment #4) > > Not sure that enabling a service and opening firewall ports simply getting > > an rpm installed as a dependency is a good idea, I'd suggest to move to doc. > > I agree. We can somehow simplify the process by providing an ansible role > for configuring a host to be ready to deploy hosted engine through cockpit, > enabling the services and opening the firewall ports. Maybe infra team > already did something in this area. Martin? We are configuring firewalld cockpit service during host-deploy [1]. Do I understand that you want to do that configuration even before host-deploy is executed for the host? If so, then I'd say this should be added into Ansible role, which executes hosted-engine installation (not sure if it already exists, but I know we have talked about it as an possible RFE to enable complete engine or hosted engine installation via Ansible role. [1] https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles/ovirt-host-deploy-firewalld/vars/firewalld_rules_common.yml#L3
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.