Bug 1720079

Summary:	[RHEL-8.1] yum update fails for rhel-8 glusterfs client packages 6.0-5.el8
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vivek Das <vdas>
Component:	build	Assignee:	Sunil Kumar Acharya <sheggodu>
Status:	CLOSED ERRATA	QA Contact:	Vivek Das <vdas>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	rhgs-3.5	CC:	amukherj, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1720615 1720620 (view as bug list)		Environment:
Last Closed:	2019-10-30 12:21:54 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:
Bug Depends On:	1720615, 1720620
Bug Blocks:	1696809

Description Vivek Das 2019-06-13 06:23:11 UTC

Description of problem:
yum update fails with the below error for RHEL-8 client packages

Error: 
 Problem 1: cannot install both glusterfs-debuginfo-6.0-5.el8.x86_64 and glusterfs-debuginfo-3.12.2-40.2.el8.x86_64
  - package glusterfs-cli-debuginfo-3.12.2-40.2.el8.x86_64 requires glusterfs-debuginfo(x86-64) = 3.12.2-40.2.el8, but none of the providers can be installed
  - cannot install the best update candidate for package glusterfs-debuginfo-3.12.2-40.2.el8.x86_64
  - problem with installed package glusterfs-cli-debuginfo-3.12.2-40.2.el8.x86_64
 Problem 2: package glusterfs-cli-3.12.2-40.2.el8.x86_64 requires glusterfs-libs(x86-64) = 3.12.2-40.2.el8, but none of the providers can be installed
  - cannot install both glusterfs-libs-6.0-5.el8.x86_64 and glusterfs-libs-3.12.2-40.2.el8.x86_64
  - cannot install the best update candidate for package glusterfs-libs-3.12.2-40.2.el8.x86_64
  - cannot install the best update candidate for package glusterfs-cli-3.12.2-40.2.el8.x86_64
 Problem 3: problem with installed package glusterfs-cli-3.12.2-40.2.el8.x86_64
  - package glusterfs-cli-3.12.2-40.2.el8.x86_64 requires glusterfs-libs(x86-64) = 3.12.2-40.2.el8, but none of the providers can be installed
  - cannot install both glusterfs-libs-6.0-5.el8.x86_64 and glusterfs-libs-3.12.2-40.2.el8.x86_64
  - package glusterfs-6.0-5.el8.x86_64 requires glusterfs-libs(x86-64) = 6.0-5.el8, but none of the providers can be installed
  - cannot install the best update candidate for package glusterfs-3.12.2-40.2.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages

Version-Release number of selected component (if applicable):
glusterfs-6.0-5.el8
RHEL-8.1

How reproducible:
Always

Steps to Reproduce:
1. Have a RHEL-8.1 system with all glusterfs packages built for rhel-8 client
2. Add latest glusterfs rhel-8 client repo
3. yum update

Actual results:
Failed to upgrade

Expected results:
Should upgrade to "6.0-5.el8"

Additional info:
Packages already available in systems
# rpm -qa | grep gluster
glusterfs-libs-3.12.2-40.2.el8.x86_64
glusterfs-rdma-3.12.2-40.2.el8.x86_64
glusterfs-rdma-debuginfo-3.12.2-40.2.el8.x86_64
glusterfs-client-xlators-debuginfo-3.12.2-40.2.el8.x86_64
glusterfs-debuginfo-3.12.2-40.2.el8.x86_64
python2-gluster-3.12.2-40.2.el8.x86_64
glusterfs-fuse-debuginfo-3.12.2-40.2.el8.x86_64
glusterfs-3.12.2-40.2.el8.x86_64
glusterfs-api-3.12.2-40.2.el8.x86_64
glusterfs-api-devel-3.12.2-40.2.el8.x86_64
glusterfs-api-debuginfo-3.12.2-40.2.el8.x86_64
glusterfs-libs-debuginfo-3.12.2-40.2.el8.x86_64
glusterfs-devel-3.12.2-40.2.el8.x86_64
glusterfs-cli-debuginfo-3.12.2-40.2.el8.x86_64
glusterfs-debugsource-3.12.2-40.2.el8.x86_64
glusterfs-client-xlators-3.12.2-40.2.el8.x86_64
glusterfs-fuse-3.12.2-40.2.el8.x86_64
glusterfs-cli-3.12.2-40.2.el8.x86_64

Comment 7 Vivek Das 2019-06-22 06:01:19 UTC

update succeeds with glusterfs-6.0-6

Comment 9 errata-xmlrpc 2019-10-30 12:21:54 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/RHEA-2019:3249