Bug 1450320
Summary: | [3.2.0_async] [RHEL7] gdeploy has to be rebuilt to be compatible with ansible 2.3 | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> | |
Component: | gdeploy | Assignee: | Sachidananda Urs <surs> | |
Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.2 | CC: | amukherj, asrivast, knarra, msaini, rcyriac, rhinduja, rhs-bugs, sasundar, smohan, storage-qa-internal, surs | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.2.0 Async | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | gdeploy-2.0.1-13 | Doc Type: | Enhancement | |
Doc Text: |
Feature:
gdeploy is updated to work with Ansible 2.3.
Reason:
Current version of ansible has removed the support for extras/ module directory in their version 2.3. gdeploy used to ship the modules which were placed in this directory.
Playbook conditional was changed in Ansible 2.3, playbooks for gdeploy had to be modified to accommodate these changes.
Result:
gdeploy installer was modified to install the modules in search path. And the playbooks updated to work with Ansible release.
|
Story Points: | --- | |
Clone Of: | 1449217 | |||
: | 1451442 (view as bug list) | Environment: | ||
Last Closed: | 2017-05-25 17:04:01 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: | ||||
Bug Depends On: | 1449217 | |||
Bug Blocks: | 1277939, 1451442 |
Description
SATHEESARAN
2017-05-12 09:14:03 UTC
Verified this bug with gdeploy-2.0.1-13.el7rhgs ansible-2.3.0.0-3.el7 In addition to comment3, tested with the basic test with ansible-2.2.3 and ansible-2.3 Kasturi has also verified the same with ansible-2.3 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:1333 |