Bug 1470943 - Convert a virt cluster to hyperconverged cluster
Summary: Convert a virt cluster to hyperconverged cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Gluster
Version: 4.1.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1523623
TreeView+ depends on / blocked
 
Reported: 2017-07-14 05:56 UTC by Sahina Bose
Modified: 2018-05-10 06:24 UTC (History)
1 user (show)

Fixed In Version: no gerrit references
Clone Of:
: 1523623 (view as bug list)
Environment:
Last Closed: 2018-05-10 06:24:00 UTC
oVirt Team: Gluster
Embargoed:
sabose: ovirt-4.2?
sabose: planning_ack?
rule-engine: devel_ack+
sasundar: testing_ack+

Attachments (Terms of Use)

Description Sahina Bose 2017-07-14 05:56:16 UTC 
Description of problem:

If user has created a virt cluster, he/she should be able to convert this cluster to also run gluster services and volumes.

- The vdsm-gluster and gluster packages should be installed on the host
- gluster services should be started

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

How reproducible:
NA
Comment 1 Sahina Bose 2018-02-21 07:44:55 UTC 
Cluster with virt service can be edited to enable gluster services. The hosts are marked non-operational if gluster command fails on the server - the hosts need to be reinstalled to ensure packages are installed and the gluster servers are peer probed.
Comment 2 SATHEESARAN 2018-05-10 03:21:05 UTC 
Verified with RHV 4.2.3 and gluster-3.12

1. Cluster with virt-service can be edited to enable gluster services.
2. If the node has installed glusterfs packages and it remains in operational state.
3. If there are no gluster packages made available ( via repo or channel ), then the node goes non-operational.
Comment 3 Sandro Bonazzola 2018-05-10 06:24:00 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.