Bug 1609550

Summary: glusterfs-resource-agents should not be built for el6
Product: [Community] GlusterFS Reporter: Niels de Vos <ndevos>
Component: buildAssignee: Niels de Vos <ndevos>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1CC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-4.1.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1609551 (view as bug list) Environment:
Last Closed: 2018-08-29 12:44:28 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: 1609551    
Bug Blocks:    

Description Niels de Vos 2018-07-29 10:23:28 UTC
Description of problem:
glusterfs-resource-agents depends on glusterfs-server and this is not available on el6 with the current Gluster releases. It is not possible to install glusterfs-resource-agents on el6 without running into dependency problems.

Version-Release number of selected component (if applicable):
4.1.2-1.el6

How reproducible:
100%

Steps to Reproduce:
1. yum -y install centos-release-gluster
2. yum -y install glusterfs-resource-agents

Actual results:
Fails to install.

Expected results:
Should not be available at all.

Additional info:
Found this issue while playing with 'repoclosure' to get it integrated in the CentOS CI for validating the yum repositories.

Comment 1 Shyamsundar 2018-08-29 12:44:28 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.1.3, please open a new bug report.

glusterfs-4.1.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-August/000111.html
[2] https://www.gluster.org/pipermail/gluster-users/