Bug 1054847

Summary:	rpm doesnt create all directories in /var/lib/glusterd
Product:	[Community] GlusterFS	Reporter:	Johan Huysmans <johan.huysmans>
Component:	build	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	bugs, johan.huysmans, kkeithle, ndevos
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-17 16:24:25 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 Johan Huysmans 2014-01-17 15:23:43 UTC

When requesting the files and directories provided by the rpm it shows many directories in /var/lib/glusterd/.
After installing that rpm those directories aren't created by the rpm and thus the /var/lib/glusterd/ directory is empty on the system.
The directories are created once the glusterd daemon is started.

On previous gluster versions these directories are created.


# rpm -qi glusterfs-server
Name        : glusterfs-server             Relocations: (not relocatable)
Version     : 3.5.0                             Vendor: Fedora Project
Release     : 0.3.beta1.el6                 Build Date: do 16 jan 2014 22:28:43 UTC
Install Date: vr 17 jan 2014 14:59:04 UTC      Build Host: buildvm-09.phx2.fedoraproject.org
Group       : System Environment/Daemons    Source RPM: glusterfs-3.5.0-0.3.beta1.el6.src.rpm
Size        : 1785022                          License: GPLv2 or LGPLv3+
Signature   : (none)
Packager    : Fedora Project
URL         : http://www.gluster.org/docs/index.php/GlusterFS
Summary     : Clustered file-system server

# rpm -ql glusterfs-server
/etc/glusterfs
/etc/glusterfs/gluster-rsyslog-5.8.conf
/etc/glusterfs/gluster-rsyslog-7.2.conf
/etc/glusterfs/glusterd.vol
/etc/glusterfs/glusterfs-georep-logrotate
/etc/glusterfs/glusterfs-logrotate
/etc/glusterfs/logger.conf.example
/etc/init.d/glusterd
/etc/init.d/glusterfsd
/etc/logrotate.d/glusterd
/etc/logrotate.d/glusterfsd
/etc/sysconfig/glusterd
/etc/sysconfig/glusterfsd
/usr/lib64/glusterfs/3.5.0beta1/xlator/features/posix-locks.so
/usr/lib64/glusterfs/3.5.0beta1/xlator/mgmt
/usr/lib64/glusterfs/3.5.0beta1/xlator/mgmt/glusterd.so
/usr/lib64/glusterfs/3.5.0beta1/xlator/nfs
/usr/lib64/glusterfs/3.5.0beta1/xlator/nfs/server.so
/usr/lib64/glusterfs/3.5.0beta1/xlator/protocol/server.so
/usr/lib64/glusterfs/3.5.0beta1/xlator/storage
/usr/lib64/glusterfs/3.5.0beta1/xlator/storage/bd.so
/usr/lib64/glusterfs/3.5.0beta1/xlator/storage/posix.so
/usr/sbin/glusterd
/usr/share/doc/glusterfs-server-3.5.0
/usr/share/doc/glusterfs-server-3.5.0/clear_xattrs.sh
/var/lib/glusterd/glusterd.info
/var/lib/glusterd/glustershd
/var/lib/glusterd/groups
/var/lib/glusterd/hooks
/var/lib/glusterd/hooks/1
/var/lib/glusterd/hooks/1/add-brick
/var/lib/glusterd/hooks/1/add-brick/post
/var/lib/glusterd/hooks/1/add-brick/pre
/var/lib/glusterd/hooks/1/create
/var/lib/glusterd/hooks/1/create/post
/var/lib/glusterd/hooks/1/create/pre
/var/lib/glusterd/hooks/1/delete
/var/lib/glusterd/hooks/1/delete/post
/var/lib/glusterd/hooks/1/delete/pre
/var/lib/glusterd/hooks/1/remove-brick
/var/lib/glusterd/hooks/1/remove-brick/post
/var/lib/glusterd/hooks/1/remove-brick/pre
/var/lib/glusterd/hooks/1/set
/var/lib/glusterd/hooks/1/set/post
/var/lib/glusterd/hooks/1/set/pre
/var/lib/glusterd/hooks/1/start
/var/lib/glusterd/hooks/1/start/post
/var/lib/glusterd/hooks/1/start/pre
/var/lib/glusterd/hooks/1/stop
/var/lib/glusterd/hooks/1/stop/post
/var/lib/glusterd/hooks/1/stop/pre
/var/lib/glusterd/nfs
/var/lib/glusterd/nfs/nfs-server.vol
/var/lib/glusterd/nfs/run
/var/lib/glusterd/nfs/run/nfs.pid
/var/lib/glusterd/options
/var/lib/glusterd/peers
/var/lib/glusterd/vols

# rpm -ql glusterfs-server | xargs ls -d 1>/dev/null
ls: cannot access /var/lib/glusterd/glusterd.info: No such file or directory
ls: cannot access /var/lib/glusterd/glustershd: No such file or directory
ls: cannot access /var/lib/glusterd/groups: No such file or directory
ls: cannot access /var/lib/glusterd/hooks: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/add-brick: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/add-brick/post: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/add-brick/pre: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/create: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/create/post: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/create/pre: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/delete: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/delete/post: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/delete/pre: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/remove-brick: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/remove-brick/post: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/remove-brick/pre: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/set: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/set/post: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/set/pre: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/start: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/start/post: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/start/pre: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/stop: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/stop/post: No such file or directory
ls: cannot access /var/lib/glusterd/hooks/1/stop/pre: No such file or directory
ls: cannot access /var/lib/glusterd/nfs: No such file or directory
ls: cannot access /var/lib/glusterd/nfs/nfs-server.vol: No such file or directory
ls: cannot access /var/lib/glusterd/nfs/run: No such file or directory
ls: cannot access /var/lib/glusterd/nfs/run/nfs.pid: No such file or directory
ls: cannot access /var/lib/glusterd/options: No such file or directory
ls: cannot access /var/lib/glusterd/peers: No such file or directory
ls: cannot access /var/lib/glusterd/vols: No such file or directory

Comment 1 Niels de Vos 2014-01-17 15:52:36 UTC

This is not an error, it is the intended behaviour. Most of these directories are created on-demand, and most of the files they contain can not be constructed before there is a configuration available. These directories and files are marked as %ghost in the rpm package, which means that the files belong to the package in case they exist, but there is no requirement for their existence.

It would be a problem if a package verification complains about the missing file. Which, for all I can see, it does not:

    # rpm --verify glusterfs-server

I'll close this as NOTABUG now, but in case you disagree, please reopen this bug an explain the problem you are facing.

Thanks,
Niels

Comment 2 Kaleb KEITHLEY 2014-01-17 16:04:35 UTC

FWIW, I just installed 3.4.2 on fedora20 and the %ghosted directories are indeed created!

Then I installed 3.5.0-0.3.beta1 (after erasing 3.4.2 and ensuring that /var/lib/glusterd was removed) and the %ghosted directories were created again.

What linux dist. did this occur on?

Comment 3 Johan Huysmans 2014-01-20 08:31:53 UTC

This happened on a centOS 6.4 system.

Comment 4 Kaleb KEITHLEY 2014-01-21 15:37:35 UTC

Confirming that what Johan saw on 6.4 also occurs on my CentOS 6.5 vm.

I'm not sure how much we would consider this a hard bug though considering we think that the dirs should not be created by the RPM install (they should be created by glusterd at run-time) and the actual bug is that they are created.

Comment 5 Niels de Vos 2016-06-17 16:24:25 UTC

This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.