+++ This bug was initially created as a clone of Bug #1635622 +++ Description of problem: ----------------------- Provide ovirt-ansible-hosted-engine-setup roles through rpms. Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHVH-4.2.7 How reproducible: ------------------ Always Actual results: --------------- ovirt-ansible-hosted-engine-setup role not available through rpms Expected results: ------------------ ovirt-ansible-hosted-engine-setup role should be available
Isn't ovirt-ansible-hosted-engine-setup role already available on RHV-H (or is this only on RHV-M)
(In reply to Sahina Bose from comment #1) > Isn't ovirt-ansible-hosted-engine-setup role already available on RHV-H (or > is this only on RHV-M) Currently we have ovirt-hosted-engine-setup rpm which contains the ansible playbooks and the interactive otopi (python) wrapper. Now we repackaged all the ansible code as a proper and reusable ansible role and we will ship it in a dedicate rpm called ovirt-ansible-hosted-engine-setup. ovirt-hosted-engine-setup will depend on ovirt-ansible-hosted-engine-setup.
Thanks Simone. So just confirming - the role rpms will be available on RHV-H?
I've targeted to 4.2.7 - I'm assuming it'll be available?
(In reply to Sahina Bose from comment #4) > I've targeted to 4.2.7 - I'm assuming it'll be available? Not committing for this to be in 4.2.7. We are in blockers only phase and this looks like an RFE. I need a very good reason for blocking 4.2.7 on this. Also please clarify: should the requested rpms be installed within RHV-H or available in RHV-H optional channel?
(In reply to Sandro Bonazzola from comment #5) > (In reply to Sahina Bose from comment #4) > > I've targeted to 4.2.7 - I'm assuming it'll be available? > > Not committing for this to be in 4.2.7. We are in blockers only phase and > this looks like an RFE. > I need a very good reason for blocking 4.2.7 on this. > > Also please clarify: should the requested rpms be installed within RHV-H or > available in RHV-H optional channel? RHV-H optional
Please note that ovirt-ansible-hosted-engine-setup depends also on ovirt-ansible-repositories.
Hi wei, Could you please help to verify this bug on RHVH side? Thanks.
Test with rhvh-4.2.7.3-0.20181017.0, cannot find the ovirt-ansible-hosted-engine-setup, ovirt-ansible-repositories and ovirt-engine-setup pacakges in the optional channel (with stage candlepin and stage cdn). Change the status to ASSIGNED.
Test Version rhvh-4.2.7.3-0.20181017.0 cockpit-ovirt-dashboard-0.11.36-1.el7ev.noarch Test Steps: 1. Clean install rhvh-4.2.7.3-0.20181017.0 2. Subscribe to stage candlepin 3. Enable all the rhel-7-server-rhvh-4* channels 4. Yum search or install the three role packages ovirt-ansible-hosted-engine-setup, ovirt-ansible-repositories and ovirt-ansible-engine-setup Result: The packages can be searched or installed successfully. Change the status to VERIFIED.
Please also check it works once installed
Test Version rhvh-4.2.7.3-0.20181017.0 cockpit-ovirt-dashboard-0.11.36-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.28-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.18-1.el7ev.noarch ovirt-ansible-repositories-1.1.2-1.el7ev.noarch ovirt-ansible-engine-setup-1.1.5-1.el7ev.noarch ovirt-ansible-hosted-engine-setup-1.0.2-1.el7ev.noarch Test Steps: 1. Clean install rhvh-4.2.7.3-0.20181017.0 2. Subscribe to stage candlepin 3. Enable all the rhel-7-server-rhvh-4* channels 4. Yum search or install the three role packages ovirt-ansible-hosted-engine-setup, ovirt-ansible-repositories and ovirt-ansible-engine-setup 5. Deploy hosted-engine via cockpit UI 6. step 1 ~ step 4 7. Config and run playbook from the guide https://github.com/oVirt/ovirt-ansible-hosted-engine-setup to using the three new role packages Result: 1. After step 5, hosted-engine can be deployed successfully(Using the ovirt-hosted-engine-setup package). 2. After step 7, hosted-engine can be deployed successfully(Using the three new role packages) so change the status to VERIFIED.
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:3476