Running ovirt-ansible-shutdown-env-1.0.4 During shutdown a warning is issued: [DEPRECATION WARNING]: The 'ovirt_host_facts' module has been renamed to 'ovirt_host_info', and the renamed one no longer returns ansible_facts. This feature will be removed in version 2.13. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. We are currently using ansible-2.9.10 so not urgent but we should get rid of the warning.
FWIW this is now emitted by many other roles we have
This requires ovirt-ansible-shutdown-env-1.0.4-1.el8ev.noarch tool on the engine, prior for the verification. Tested on: ovirt-ansible-shutdown-env-1.0.4-1.el8ev.noarch ansible-2.9.13-1.el8ae.noarch ovirt-ansible-engine-setup-1.2.4-1.el8ev.noarch ovirt-ansible-hosted-engine-setup-1.1.8-1.el8ev.noarch vdsm-4.40.26.1-1.el8ev.x86_64 ovirt-hosted-engine-setup-2.4.6-2.el8ev.noarch ovirt-hosted-engine-ha-2.4.4-1.el8ev.noarch rhvm-appliance-4.4-20200722.0.el8ev.x86_64 1.I manually installed latest ovirt-ansible-shutdown-env-1.0.4-1.el8ev.noarch instead of an old ovirt-ansible-shutdown-env-1.1.0-1.el8ev.noarch.rpm, which came with the appliance. 2.I manually created shutdown.yml with the following: --- - name: oVirt shutdown env hosts: localhost connection: local gather_facts: false vars_files: # Contains encrypted `engine_password` varibale using ansible-vault #- passwords.yml vars: engine_url: https://nsednev-he-1.qa.lab.tlv.redhat.com/ovirt-engine/api engine_user: admin@internal engine_password: 123456 engine_cafile: /etc/pki/ovirt-engine/ca.pem roles: - ovirt.shutdown_env 3.I ran ansible-playbook -i localhost. shutdown.yml, for the run of the script results please check the attachment. 4.All guest-vms were shutdown and then ha-host with the engine itself, just like expected. I didn't observed previously reported [DEPRECATION WARNING] issue. Moving to verified.
Created attachment 1713879 [details] shutdownrun
This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.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.