Bug 1359236 - [RFE] Support Ansible v2+ for OpenShift Playbooks
Summary: [RFE] Support Ansible v2+ for OpenShift Playbooks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ---
: ---
Assignee: Andrew Butcher
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-22 14:55 UTC by Eric Jones
Modified: 2022-04-25 14:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
The OpenShift Enterprise 3.2 playbooks now require Ansible 2.x.
Clone Of:
Environment:
Last Closed: 2016-08-18 19:29:29 UTC
Target Upstream Version:
Embargoed:
abutcher: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1639 0 normal SHIPPED_LIVE OpenShift Enterprise atomic-openshift-utils bug fix and enhancement update 2016-08-18 23:26:45 UTC

Description Eric Jones 2016-07-22 14:55:34 UTC
- What is the nature and description of the request? 
As an admin I require the ability to use Ansible v2+ to run the OpenShift Playbooks as that is what is used elsewhere.

- Why does the customer need this? (List the business requirements here) 
Previous usage of Ansible v2

Comment 3 Johnny Liu 2016-08-16 05:32:28 UTC
Verified this bug with ansible-2.2.0-0.5.prerelease.el7.noarch in AtomicOpenShift-errata/3.2/2016-08-15.1, and PASS.


openshift is installed successfully using ansible v2+, and do some basic testing, no issue found.

Comment 6 errata-xmlrpc 2016-08-18 19:29:29 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/RHBA-2016:1639


Note You need to log in before you can comment on or make changes to this bug.