Bug 1725703

Summary:	[RHEL-7.7 RHGS-34] yum update for RHEL-7.7 Snap-3 fails with for sos package conflict with live rhgs vdsm package
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vivek Das <vdas>
Component:	vdsm	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	Vivek Das <vdas>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	rhgs-3.4	CC:	amukherj, asriram, godas, puebele, rcyriac, rhs-bugs, rhsc-qe-bugs, sankarshan, sasundar, storage-qa-internal
Target Milestone:	---	Keywords:	Regression, ZStream
Target Release:	RHGS 3.4.z Async Update
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Rebase: Bug Fixes Only
Doc Text:	The VDSM package has been upgraded to version 4.30, which provides a number of bug fixes and enhancements over the previous version.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-30 10:04:09 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 Vivek Das 2019-07-01 09:40:22 UTC

Description of problem:

The newer version of 'sos' package is getting shipped with RHEL-7.7. Which conflicts with live RHGS vdsm package i.e "vdsm-4.19.43-2.3.el7rhgs.x86_64" resulting in update failure.

Version-Release number of selected component (if applicable):
RHGS-3.4 live
vdsm installed vdsm-4.19.43-2.3.el7rhgs.x86_64
sos (rhel-7.7) sos-3.7-4.el7.noarch
Expected vdsm >= 4.30.17

How reproducible:
Always

Steps to Reproduce:
1. RHEL-7.6 RHGS-3.4.4 live machine
2. Add RHEL-7.7 snap3 repo
3. yum update

Actual results:
Error: sos conflicts with vdsm-4.19.43-2.3.el7rhgs.x86_64

Expected results:
Should succeed with conflict or error

Additional info:

--> Processing Conflict: sos-3.7-4.el7.noarch conflicts vdsm <= 4.30.17
--> Finished Dependency Resolution
Error: sos conflicts with vdsm-4.19.43-2.3.el7rhgs.x86_64

Comment 12 errata-xmlrpc 2019-07-30 10:04:09 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-2019:1965