Bug 1539656 - Deploying a node in HC cluster fails due to cgroups role
Summary: Deploying a node in HC cluster fails due to cgroups role
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Gluster
Version: 4.1.7.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.2.1
: 4.2.1.6
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 11:55 UTC by Sahina Bose
Modified: 2018-05-10 06:28 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.2.1.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-10 06:28:23 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+
sabose: devel_ack+
sasundar: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86878 0 master MERGED gluster: Correct the hc-cgroups role 2018-01-30 10:15:21 UTC
oVirt gerrit 87160 0 ovirt-engine-4.2.1.z MERGED gluster: Correct the hc-cgroups role 2018-02-05 14:58:00 UTC

Description Sahina Bose 2018-01-29 11:55:15 UTC 
Description of problem:

While deploying a node to HC cluster, the gluster-cgroups role fails as the glusterd overrides directory is not present in systemd folder

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


How reproducible:
Always

Steps to Reproduce:
1. Add a node to an HC cluster


Actual results:
Comment 1 Sahina Bose 2018-01-29 17:18:37 UTC 
Adding as blocker since gluster nodes cannot be added to cluster.
Comment 3 SATHEESARAN 2018-05-10 03:11:02 UTC 
Tested with RHV 4.2.3 and gluster-3.12
1. gluster cgroups role works
2. Proper slice information set on the node
Comment 4 Sandro Bonazzola 2018-05-10 06:28:23 UTC 
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 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.