Description of problem: Ansible deprecation warnings are presented to the user while installing Hosted-engine. [ INFO ] TASK [Remove host-deploy configuration file] [ INFO ] changed: [localhost] [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: How reproducible: 100% Steps to Reproduce: 1. run hosted-engine --deploy with default answers Actual results: deprecation warnings are shown as Errors Expected results: no Ansible warnings should appear Additional info:
We need another BZ to fix those deprecated items.
On the other hand, we do want to view those warnings and handle them when they appear.
Works for me on these components: ovirt-hosted-engine-setup-2.2.18-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.10-1.el7ev.noarch rhvm-appliance-4.2-20180420.0.el7.noarch Linux 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.5 (Maipo)
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 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.