Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1354489

Summary: service file is executable
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: mainlineCC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://bugs.archlinux.org/task/50001
Whiteboard:
Fixed In Version: glusterfs-3.9.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1354476
: 1354499 (view as bug list) Environment:
Last Closed: 2017-03-27 18:18:00 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:
Bug Depends On:    
Bug Blocks: 1354476, 1354499    

Description Niels de Vos 2016-07-11 12:23:03 UTC
+++ This bug was initially created as a clone of Bug #1354476 +++

Description of problem:
journalctl -fa
juil. 09 08:38:37 raptor.seblu.net systemd[1]: Configuration file /usr/lib/systemd/system/glusterd.service is marked executable. Please remove executable permission bits. Proceeding anyway.

Version-Release number of selected component (if applicable):
3.7.11

How reproducible:
100%

Steps to Reproduce:
1. build and install a glusterfs package
2. check permissions of /usr/lib/systemd/system/glusterd.service

Actual results:
/usr/lib/systemd/system/glusterd.service is executable

Expected results:
/usr/lib/systemd/system/glusterd.service should not be executable

Additional info:

Comment 1 Vijay Bellur 2016-07-11 12:27:20 UTC
REVIEW: http://review.gluster.org/14892 (build: systemd unit should not be marked executable) posted (#1) for review on master by Niels de Vos (ndevos@redhat.com)

Comment 2 Vijay Bellur 2016-07-11 13:25:04 UTC
REVIEW: http://review.gluster.org/14892 (build: systemd unit should not be marked executable) posted (#2) for review on master by Niels de Vos (ndevos@redhat.com)

Comment 3 Vijay Bellur 2016-07-11 21:20:51 UTC
REVIEW: http://review.gluster.org/14892 (build: systemd unit should not be marked executable) posted (#3) for review on master by Niels de Vos (ndevos@redhat.com)

Comment 4 Vijay Bellur 2016-07-19 11:00:09 UTC
REVIEW: http://review.gluster.org/14892 (build: systemd unit should not be marked executable) posted (#4) for review on master by Niels de Vos (ndevos@redhat.com)

Comment 5 Vijay Bellur 2016-07-19 11:11:43 UTC
REVIEW: http://review.gluster.org/14892 (build: systemd unit should not be marked executable) posted (#5) for review on master by Niels de Vos (ndevos@redhat.com)

Comment 6 Vijay Bellur 2016-08-05 13:17:22 UTC
REVIEW: http://review.gluster.org/14892 (build: systemd unit should not be marked executable) posted (#6) for review on master by Niels de Vos (ndevos@redhat.com)

Comment 7 Vijay Bellur 2016-08-08 01:05:09 UTC
COMMIT: http://review.gluster.org/14892 committed in master by Kaleb KEITHLEY (kkeithle@redhat.com) 
------
commit 9f22282795e20fd62b22847b92dffd0cde9cca1b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jul 19 12:55:03 2016 +0200

    build: systemd unit should not be marked executable
    
    systemd complains about the unit for GlusterD when it is executable:
    
      Configuration file /usr/lib/systemd/system/glusterd.service is marked executable. Please remove executable permission bits. Proceeding anyway.
    
    The Makefile that installs the unit has some scripted commands. These
    are not needed and standard "*dir" and "*DATA" postfixes for variables
    can be used instead.
    
    The EXTRA_DIST variable is needed for building the 'make dist' tarball
    on systems where there is no systemd. The unit would be missing from the
    tarball if it is not explicitly included.
    
    BUG: 1354489
    Change-Id: I5e72ec201036906b9b2458bc8931ccebf9a8c6b4
    Reported-by: Sergej Pupykin <ml@sergej.pp.ru>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14892
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

Comment 8 Shyamsundar 2017-03-27 18:18:00 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.9.0, please open a new bug report.

glusterfs-3.9.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/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/