Bug 1581682 - [RFE] gdeploy should support ansible 2.5
Summary: [RFE] gdeploy should support ansible 2.5
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.5
Assignee: Sahina Bose
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On: 1581649
Blocks: 1520833
TreeView+ depends on / blocked
 
Reported: 2018-05-23 12:07 UTC by SATHEESARAN
Modified: 2019-05-20 04:54 UTC (History)
7 users (show)

Fixed In Version: gdeploy-2.0.2-27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1581649
Environment:
Last Closed: 2019-05-20 04:54:59 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2018-05-23 12:07:41 UTC
+++ This bug was initially created as a clone of Bug #1581649 +++

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

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-05-23 06:00:00 EDT ---

This bug is automatically being proposed for the release of Red Hat Gluster Storage 3 under active development and open for bug fixes, by setting the release flag 'rhgs‑3.4.0' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 2 SATHEESARAN 2018-05-24 12:38:41 UTC
Moving the state of the bug to ON_QA, as the gdeploy bug is already ON_QA

Comment 3 SATHEESARAN 2018-05-24 12:39:20 UTC
Mistakenly moved to VERIFIED, moving it to correct state - ON_QA

Comment 4 Mugdha Soni 2018-06-19 11:54:59 UTC
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.


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