Bug 1410853

Summary:	glusterfs-server should depend on firewalld-filesystem
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	packaging	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, kkeithle
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1410852
Clones:	1410854 (view as bug list)		Environment:
Last Closed:	2017-03-06 17:42:42 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:
Bug Blocks:	1410852, 1410854

Description Niels de Vos 2017-01-06 15:54:40 UTC

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

Description of problem:
Recently RHEL7 was rebased to have firewalld-filesystem available. Because the glusterfs-server RPM installs a .xml file with firewalld rules, this RPM needs to depend on the RPM that provides the directory for the .xml files.

Version-Release number of selected component (if applicable):
3.8 and newer

Additional info:
The glusterfs.spec.in currently tries to execute "firewall-cli --reload". The correct way is to call the %firewalld_reload macro from /usr/lib/rpm/macros.d/macros.firewalld (provided by firewalld-filesystem).

Comment 1 Worker Ant 2017-01-06 16:18:09 UTC

REVIEW: http://review.gluster.org/16351 (rpm: depend on firewalld-filesystem for directory ownership) posted (#1) for review on master by Niels de Vos (ndevos)

Comment 2 Worker Ant 2017-01-06 16:52:00 UTC

REVIEW: http://review.gluster.org/16351 (rpm: depend on firewalld-filesystem for directory ownership) posted (#2) for review on master by Niels de Vos (ndevos)

Comment 3 Worker Ant 2017-01-10 02:17:56 UTC

COMMIT: http://review.gluster.org/16351 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit f99750b4477538cd1f97ce6340e1813202f986e2
Author: Niels de Vos <ndevos>
Date:   Fri Jan 6 17:16:38 2017 +0100

    rpm: depend on firewalld-filesystem for directory ownership
    
    Also use the %firewalld_reload macro that is provided by the
    firewalld-filesystem package.
    
    BUG: 1410853
    Change-Id: Ibbbc18cc394f8b1e5ba74927effc41c466667479
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: http://review.gluster.org/16351
    Smoke: Gluster Build System <jenkins.org>
    Tested-by: Kaleb KEITHLEY <kkeithle>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 4 Worker Ant 2017-01-13 13:33:55 UTC

REVIEW: http://review.gluster.org/16408 (rpm: fix glusterfs-server(%postun) scriptlet error) posted (#1) for review on master by Niels de Vos (ndevos)

Comment 5 Worker Ant 2017-01-13 20:16:35 UTC

COMMIT: http://review.gluster.org/16408 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit 2041fb7872fa6672e9164fd2a12aaf80e6ef3ebd
Author: Niels de Vos <ndevos>
Date:   Fri Jan 13 14:31:27 2017 +0100

    rpm: fix glusterfs-server(%postun) scriptlet error
    
    While introducing the usage of the %firewalld_restart macro, the old
    scriplet was not correctly removed. This causes an error to be displayed
    when the RPM gets updated or uninstalled.
    
    Fixes: f99750b4477538cd1f97ce6340e1813202f986e2
    Change-Id: I69091d8e9e3c412dc3cb52246967eac29d2ebc90
    BUG: 1410853
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: http://review.gluster.org/16408
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 6 Shyamsundar 2017-03-06 17:42:42 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-3.10.0, please open a new bug report.

glusterfs-3.10.0 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] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/