[Bugs] [Bug 1206065] New: [Backup]: 'Glusterfind create' creates a sub-directory at $glusterd_working_directory/session_dir even when the command fails

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1206065

            Bug ID: 1206065
           Summary: [Backup]: 'Glusterfind create' creates a sub-directory
                    at $glusterd_working_directory/session_dir even when
                    the command fails
           Product: GlusterFS
           Version: mainline
         Component: unclassified
          Assignee: bugs at gluster.org
          Reporter: sanandpa at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

'Glusterfind create' creates a directory for every session that is created, and
a subdirectory under it, with the volume name. When the command is given for a
non-existent volume, 'glusterfind create' command fails, as expected. But a
sub-directory is created under the session directory with the
non-existent-volume name.

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

Glusterfs upstream nightly glusterfs-server-3.7dev-0.777.git2308c07.el6.x86_64

How reproducible: Always


Steps to Reproduce:

1. Have a cluster, with 2*2 gluster vol 'ozone'

2. Run the glusterfind create command with non-existent volume name.
glusterfind create <sessionName> <volumeName>
glusterfind create session1 oz

3. The command fails. Check at /etc/glusterfs/glusterd.vol as to what is the
working directory. Check in that location if a directory with the name
'session1' is created and if that is empty.

Actual results:
Sub-directory 'oz' is created under $session_dir

Expected results: 
No sub-directory should not be created, if the glusterfind create command has
failed.

Additional info: 

[root at dhcp43-140 ~]# gluster v i

Volume Name: ozone
Type: Distributed-Replicate
Volume ID: cd2a06e9-fea0-4e69-98f9-9fd46e915c46
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.43.140:/rhs/brick1/dd
Brick2: 10.70.42.75:/rhs/brick1/dd
Brick3: 10.70.43.140:/rhs/brick2/dd
Brick4: 10.70.42.75:/rhs/brick2/dd
Options Reconfigured:
changelog.changelog: on
storage.build-pgfid: on
[root at dhcp43-140 ~]#
[root at dhcp43-140 ~]# glusterfind create session1 ozn
Failed to set volume option build-pgfid on: volume set: failed: Volume ozn does
not exist
[root at dhcp43-140 ~]#
[root at dhcp43-140 ~]# glusterfind create session1 ozone
[root at dhcp43-140 ~]# cd /etc/glusterfs/
glusterd.vol                glusterfs-logrotate        
gluster-rsyslog-7.2.conf    logger.conf.example
glusterfs-georep-logrotate  gluster-rsyslog-5.8.conf    group-virt.example      
[root at dhcp43-140 ~]# cat /etc/glusterfs/glusterd.vol 
volume management
    type mgmt/glusterd
    option working-directory /var/lib/glusterd
    option transport-type socket,rdma
    option transport.socket.keepalive-time 10
    option transport.socket.keepalive-interval 2
    option transport.socket.read-fail-log off
    option ping-timeout 30
#   option base-port 49152
end-volume
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# cd /var/lib/glusterd/glusterfind/session1/oz
ozn/   ozone/ 
[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# glusterfind create session1 oz
Failed to set volume option build-pgfid on: volume set: failed: Volume oz does
not exist

[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# cd /var/lib/glusterd/glusterfind/session1/oz
oz/    ozn/   ozone/ 
[root at dhcp43-140 ~]#

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.