Description of problem:
When using firewalld cluster without installing ovirt-ansible, host vdsm is unreachable from engine, but there is no notification to the user in the admin portal.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install engine in dev env
2. run engine
3. create a host on engine
==> after initial setup of vdsm on host is finished and engine tries to connect to vdsm on host, vdsm is unreachable because the firewall has not been configured (if firewalld is stopped host vdsm becomes reachable from host).
There is no event or notification in the admin portal that indicates why the status of the host has become unreachable.
event indicating problem should be written to the admin portal, and significant status should be displayed in the hosts table view
As far as I understand such a use case isn't possible when installing oVirt properly. Am I right?
Perhaps the Dev environment Readme should be improved to make sure you install new required packages.
on a clean 4.2 customer installation, I believe that ovirt-ansible would be installed, and this precise bug would not be seen. I am less sure about upgrades.
However, if Ansible fails for whatever reason, add-host should report a failure. Currently it is failing silently.
The Dev Readme is now up to date.
Attaching relevant logs
2017-09-27 13:34:32,049+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.EE-ManagedThreadFactory-engine-Thread-1) [7379abf9] EVENT_ID: VDS_ANSIBLE_INSTALL_STARTED(560), Ansible host-deploy playbook execution has started on host h-local-1.
2017-09-27 13:34:32,050+03 WARN [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (org.ovirt.thread.EE-ManagedThreadFactory-engine-Thread-1) [7379abf9] Playbook '/home/eraviv/ov/dep/ovirt-engine-1/share/ovirt-engine/../ovirt-ansible-roles/playbooks/ovirt-host-deploy.yml' does not exists. Playbook won't be executed.
2017-09-27 13:34:32,054+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.EE-ManagedThreadFactory-engine-Thread-1) [7379abf9] EVENT_ID: VDS_ANSIBLE_INSTALL_FINISHED(561), Ansible host-deploy playbook execution has successfully finished on host h-local-1.
Created attachment 1333177 [details]
Created attachment 1333178 [details]
host deploy log
ovirt-engine depends on ovirt-ansible-roles package, so in RPM installation the ovirt-host-deploy role should always be present, but you are right, we should fail the host deploy process if the role is for example removed by accident.
Playbooks became part of ovirt-engine-tools.rpm and it depends on main ovirt-engine.rpm
Not an issue anymore
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.
Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.