Bug 1365832

Summary:	Remove vdsm-reg dependency from redhat-storage-server on RHEL7
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sahina Bose <sabose>
Component:	redhat-storage-server	Assignee:	Milind Changire <mchangir>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	amukherj, asrivast, dnarayan, mmalhotr, nlevinki, rcyriac, rhinduja, rhs-bugs, rhsc-qe-bugs, rnachimu, sabose, sanandpa, sankarshan, sasundar, sgirijan, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.3 Async
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Deprecated Functionality
Doc Text:	This release deprecates the usage vdsm-reg package.	Story Points:	---
Clone Of:	1213383	Environment:
Last Closed:	2016-08-23 04:24:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sahina Bose 2016-08-10 10:16:18 UTC

+++ This bug was initially created as a clone of Bug #1213383 +++

vdsm in rhgs 3.1 is rebased to 3.6 cluster level (vdsm 4.17)  on RHEL 7. vdsm 4.17.x no longer has a vdsm-reg package. redhat-storage-server has a dependency on this package and fails to install.

Need to remove this dependency from redhat-storage-server

Comment 1 Atin Mukherjee 2016-08-11 04:53:51 UTC

qe flag is disturbed here due to component change. Would you mind to ack it back?

Comment 2 Milind Changire 2016-08-16 05:59:01 UTC

build for RHEL 7 is now available at:
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=509196

Comment 6 SATHEESARAN 2016-08-17 16:53:34 UTC

Tested with redhat-storage-server-3.1.3.0-4.el7rhgs and this package no longer pulls vdsm-reg as a dependency

[root@ ]# rpm -qpR redhat-storage-server-3.1.3.0-4.el7rhgs.noarch.rpm|grep -i vdsm
vdsm-gluster

Comment 8 errata-xmlrpc 2016-08-23 04:24:12 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://rhn.redhat.com/errata/RHBA-2016-1651.html