Description of problem:
This build has ansible-2.2.0.0-1.el7.noarch while it should have 2.3.0.0: https://errata.devel.redhat.com/advisory/28325
Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.1-20170531.0
imgbased-0.9.30-0.1.el7ev.noarch
ansible-2.2.0.0-1.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install redhat-virtualization-host-4.1-20170531.0
2. Login RHVH, check ansible version
[root@dhcp-9-52 ~]# rpm -q ansible
ansible-2.2.0.0-1.el7.noarch
Actual results:
1. After step 2, include wrong version of ansible in redhat-virtualization-host-4.1-20170531.0
Expected results:
1. After step2, RHVH should include ansible-2.3.0.0.
Additional info:
This is a conflict between RHGS tags and RHEV tags.
Sahina -
RHGS includes ansible 2.2.0 (which is pulled into rhgs-rhvh-4.1-rhel-7-pending). Does ansible work with 2.3.0? Can we remove this from rhgs-rhvh-4.1-rhel-7-pending?
Just verified on rhvh-4.1-0.20170609.0+1, the ansible was update to ansible-2.3.0.0-4.el7.noarch
[root@dhcp-9-52 ~]# imgbase w
2017-06-13 05:41:58,449 [INFO] You are on rhvh-4.1-0.20170609.0+1
[root@dhcp-9-52 ~]# rpm -q imgbased
imgbased-0.9.31-0.1.el7ev.noarch
[root@dhcp-9-52 ~]# rpm -qa|grep ansible
ansible-2.3.0.0-4.el7.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-2017:1714