Bug 1676405 - Use ansible modules rather than gdeploy modules in brick creation flow from RHV-M
Summary: Use ansible modules rather than gdeploy modules in brick creation flow from R...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: RHHI-V 1.6
Assignee: Sahina Bose
QA Contact: bipin
URL:
Whiteboard:
Depends On: 1676406
Blocks: RHHI-V-1-6-Engineering-RFE-BZs
TreeView+ depends on / blocked
 
Reported: 2019-02-12 08:26 UTC by Gobinda Das
Modified: 2019-05-09 06:09 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.3.2.1
Doc Type: Enhancement
Doc Text:
Previously, when users deployed Red Hat Hyperconverged Infrastructure for Virtualization using the Cockpit UI, gdeploy was used to create and configure bricks. Gdeploy is now replaced by gluster-ansible roles, which integrate better with ovirt-ansible roles.
Clone Of:
: 1676406 (view as bug list)
Environment:
Last Closed: 2019-05-09 06:09:09 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1121 0 None None None 2019-05-09 06:09:21 UTC

Description Gobinda Das 2019-02-12 08:26:21 UTC 
Description of problem:
 Now the brick creation uses gdeploy to create pv. As we are going to replace gdeploy with ansible role, the brick creation flow also need to use ansible module rather than gdeploy module.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 bipin 2019-03-15 08:01:28 UTC 
Moving the bug to verified as the brick creation works without gdeploy.

Components:
===========
ansible-2.7.6-1.el7ae.noarch
ovirt-engine-4.3.2.1-0.1.el7.noarch
Comment 4 errata-xmlrpc 2019-05-09 06:09:09 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-2019:1121
Note You need to log in before you can comment on or make changes to this bug.