Newly introduced ovirt-ansible-collection package will contain not only all existing oVirt Ansible modules, but we also want to migrate disaster-recovery standalone role into ovirt-ansible-collection package. oVirt Ansible Collection will not only be distributed as RPM package, but it should be also available from Red Hat Automation Hub as supported collection
Comments to QE regarding what has changed while moving to Ansible Collection: in general not much from the functionality PoV. 1) CI warnings - didn't change the logic. 2) README.md updates 3) Multiple code changes that *do not* change the logic: a) Removing unused variables. b) Renaming variables. c) Fixing typos in fixing/improving user messages/logs. d) Code simplification & reformatting. e) Some internal implementation files were moved to different location under the new project. f) Updating the default paths. g) Removing redundant configuration parameter "vault" from the validator step. 4) Minot bug-fixes: a) Validator step - using default var file path correctly (instead of an empty path if user just presses <ENTER>, thus choosing the suggested default path) when the configured var file was not properly initialized (does not appear in "dr.conf" or doesn't exist on disk). b) Same as above issue with the default Ansible play file in failover & failback flows. c) Add default parameter for the var file for the "failover" & "failback" flows. 5) Bug-fixes: a) Adding "~" support in paths received from the user (either from configuration file "dr.conf" or from CLI when the file path received from "dr.conf" file doesn't exist). So generally speaking, from the user/QE no functionality changed, except moving to Ansible Collection.
Verified on rhv 4.4.4-2 using the full flow of 'active - passive' DR manually done, including failover and failback flows. Using NFS storage.
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.4 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.