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
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: vdsm
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: ---
: RHGS 3.2.0 Async
Assignee: Sahina Bose
QA Contact: Sweta Anandpara
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-19 06:32 UTC by SATHEESARAN
Modified: 2017-08-01 06:55 UTC (History)
8 users (show)

Fixed In Version: vdsm-4.17.33-1.2.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 06:55:50 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2340 0 normal SHIPPED_LIVE vdsm bug fix update 2017-08-01 10:55:40 UTC

Description SATHEESARAN 2017-07-19 06:32:49 UTC
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 06:55:50 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/RHBA-2017:2340


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