+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1570608 +++ ====================================================================== Description of problem: Due to the difference between upstream and downstream deployment mechanism for Manageiq/Cloudforms which on downstream requires a init command for the appliance, the role fails on bringing CF up and configure RHV as a provider inside. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.use the default playbook in the examples provided in the ovirt ansible roles RPM 2. 3. Actual results: Expected results: Additional info: (Originally by Moran Goldboim)
Deferring to 4.2.4. Moran - please attach the requirements docs for the feature (I have not been able to find it). (Originally by Yaniv Kaul)
(In reply to Yaniv Kaul from comment #1) > Deferring to 4.2.4. > Moran - please attach the requirements docs for the feature (I have not been > able to find it). I can't find it as well right now, but this is a supported role from 4.1 release. it's simply doesn't work the same way with CloudForms between upstream and downstream. a patch (https://github.com/oVirt/ovirt-ansible-manageiq/pull/37) that fixes the problem already there, and validated by me. QE has approved to consume this change and test it. not sure why the conditional nack, or pushing it to zstream when we know this function is broken and we have a fix. (Originally by Moran Goldboim)
We have a proposed fix upstream, that's all. Moving to POST. I think the patch is good and I hope it can make it to GA. If not, since it's clearly not a blocker (I don't see the requirements the support for CFME - I don't recall 4.1 supported it as well, it's not even documented anywhere in our d/s docs), it is now targeted to the 1st z-stream. (Originally by Yaniv Kaul)
Verified in ovirt-ansible-manageiq-1.1.10-1.el7ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2069
BZ<2>Jira Resync