Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1581649 - gdeploy should support ansible 2.5
gdeploy should support ansible 2.5
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy (Show other bugs)
3.3
x86_64 Linux
unspecified Severity high
: ---
: RHGS 3.3.1 Async
Assigned To: Sachidananda Urs
Manisha Saini
: ZStream
Depends On:
Blocks: 1581682 1581561
  Show dependency treegraph
 
Reported: 2018-05-23 05:59 EDT by SATHEESARAN
Modified: 2018-06-20 23:34 EDT (History)
6 users (show)

See Also:
Fixed In Version: gdeploy-2.0.2-26
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1581682 (view as bug list)
Environment:
Last Closed: 2018-06-20 23:33:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1958 None None None 2018-06-20 23:34 EDT

  None (edit)
Description SATHEESARAN 2018-05-23 05:59:54 EDT
Description of problem:
-----------------------
gdeploy should extend support with ansible 2.5

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
ansible-2.5.z
gdeploy-2.0.2

How reproducible:
------------------
Not available

Expected results:
--------------------
gdeploy should support ansible 2.5
Comment 4 Mugdha Soni 2018-06-19 07:55:45 EDT
Tested with the following :-
(1)ansible-2.5.5-1.el7ae.noarch
(2)gdeploy-2.0.2-27.el7rhgs.noarch

The deployment testing with RHHI was successful so moving the bug to verified state.
Comment 6 errata-xmlrpc 2018-06-20 23:33:15 EDT
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-2018:1958

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