Bug 1472623 – Unable to manage RHGS Node based on RHEL 7.4 with RHSCv1/RHV

Bug 1472623 - Unable to manage RHGS Node based on RHEL 7.4 with RHSCv1/RHV

Summary:	Unable to manage RHGS Node based on RHEL 7.4 with RHSCv1/RHV

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	vdsm (Show other bugs)
Sub Component:
Version:	3.2
Hardware:	x86_64 Linux

Priority	high Severity urgent
Target Milestone:	---
Target Release:	RHGS 3.2.0 Async
Assigned To:	Sahina Bose
QA Contact:	Sweta Anandpara
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-07-19 02:32 EDT by SATHEESARAN
Modified:	2017-08-01 02:55 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	vdsm-4.17.33-1.2.el7rhgs
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-01 02:55:50 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description SATHEESARAN 2017-07-19 02:32:49 EDT

Description of problem:
-----------------------
RHGS node based on RHEL 7.4 can't be managed with RHSCv1 or RHV 4.1.3

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS-Console 3.2
RHV-4.1.3
vdsm-4.17-33-1.el7rhgs ( shipped in RHGS )

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Create a DC ( compatibility 3.6 )
2. Create a gluster only cluster of 3.6 cluster compatibility 
3. Add RHGS node based on RHEL 7.4 to the cluster

Actual results:
---------------
The node doesn't comes up operational

Expected results:
-----------------
The RHGS node should come up operational

Additional info:
----------------
This bug ( BZ 1444426 ) is already root caused and fixed with the latest vdsm-4.19.

Comment 8 errata-xmlrpc 2017-08-01 02:55:50 EDT

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:2340

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