This seems to be a much bigger generic issue with Ansible 2.9. Here is an 
excerpt from the release notes:

"Renaming from _facts to _info

Ansible 2.9 renamed a lot of modules from <something>_facts to 
<something>_info, because the modules do not return Ansible facts. Ansible 
facts relate to a specific host. For example, the configuration of a network 
interface, the operating system on a unix server, and the list of packages 
installed on a Windows box are all Ansible facts. The renamed modules return 
values that are not unique to the host. For example, account information or 
region data for a cloud provider. Renaming these modules should provide more 
clarity about the types of return values each set of modules offers."

I guess that means all the oVirt playbooks need to be adapted for Ansible 2.9 
and that evidently didn't happen or not completely.

It would also seem to suggest that there is no automated integration testing 
before an oVirt release... which contradicts the opening clause of the opening 
phrase of the ovirt.org download page: "oVirt 4.3.7 is intended for production 
use and is available for the following platforms..."
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/ROWX54XPPIGHBDRYR6VRHVFXD4WZ4VBM/

Reply via email to