Bug 1349036

Summary:	ceph-ansible should explicitly require ansible < 2
Product:	[Red Hat Storage] Red Hat Storage Console	Reporter:	Ken Dreyer (Red Hat) <kdreyer>
Component:	ceph-ansible	Assignee:	Ken Dreyer (Red Hat) <kdreyer>
Status:	CLOSED ERRATA	QA Contact:	Rachana Patel <racpatel>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2	CC:	adeza, aschoen, ceph-eng-bugs, ceph-qe-bugs, hnallurv, nthomas, sankarshan
Target Milestone:	---
Target Release:	2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-ansible-1.0.5-23.el7scon ceph-installer-1.0.12-3.el7cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:55:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ken Dreyer (Red Hat) 2016-06-22 14:47:37 UTC

Description of problem:
We have only tested ceph-ansible with Ansible 1.9 in the RHSCON repository. We should update the ceph-ansible package to explicitly require Ansible 1.9, so that if a customer has access to a newer Ansible RPM, it will not be upgraded.

Version-Release number of selected component (if applicable):
ceph-ansible-1.0.5-22.el7scon

How reproducible:
always

Steps to Reproduce:
1. Set up a RHEL 7 node
2. Activate EPEL
3. yum install ceph-ansible

Actual results:
Ansible 2 from EPEL is installed.

Expected results:
Ansible 1.9 is installed.

Comment 1 Ken Dreyer (Red Hat) 2016-06-22 15:22:48 UTC

Change submitted upstream: https://github.com/ceph/ceph-installer/pull/161

Comment 3 Ken Dreyer (Red Hat) 2016-06-22 16:28:38 UTC

It turns out EPEL was probably a poor example above, since EPEL ships its own "ansible19" package. But since EPEL is unsupported anyway, this is good enough, I think. The main goal is to avoid upgrading to Ansible 2 from another Red Hat product.

Comment 10 errata-xmlrpc 2016-08-23 19:55:51 UTC

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/RHEA-2016:1754