[Bugs] [Bug 1225565] New: [Backup]: RFE - Glusterfind CLI commands need to respond based on volume's start/stop state

[bugzilla at redhat.com]

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

            Bug ID: 1225565
           Summary: [Backup]: RFE - Glusterfind CLI commands need to
                    respond based on volume's start/stop state
           Product: GlusterFS
           Version: 3.7.0
         Component: glusterfind
          Keywords: FutureFeature
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: avishwan at redhat.com
        QA Contact: bugs at gluster.org
                CC: avishwan at redhat.com, bugs at gluster.org,
                    khiremat at redhat.com, mchangir at redhat.com,
                    sanandpa at redhat.com
        Depends On: 1224236, 1225564
            Blocks: 1223636



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

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

Description of problem:
If a volume is in a stopped state, glusterfind create succeeds (!). And the pre
fails with the error 'Changelog register failed- Connection refused'. Post and
delete succeeds. It is required to have a uniform behaviour of glusterfind CLI
commands, depending on the start/stop state of the volume. 

This could be further enhanced to gracefully handle the scenario where the
volume goes into a stopped state, in the middle of a pre command being run.

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


How reproducible: Always


Steps to Reproduce:
1. Create a new volume. Leave it in a stopped state
2. Create a glusterfind session. That succeeds.
3. Execute glusterfind pre and that fails with an error. 
4. Delete the glusterfind session and the session gets deleted.


Expected results:

* Step 3 should gracefully fail with a more related error.
* All glusterfind CLI commands - create/pre/post/delete/list - should have
uniform behaviour based on the state of the volume.

Additional info:

[root at dhcp43-140 ~]# 
[root at dhcp43-140 ~]# gluster v stop nash
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
y
volume stop: nash: success
[root at dhcp43-140 ~]# glusterfind pre sess_nash nash /tmp/out.txt
--regenerate-outfile
10.70.43.140 - pre failed: /rhs/thinbrick2/nash/dd Changelog register failed:
[Errno 111] Connection refused

10.70.43.140 - pre failed: /rhs/thinbrick1/nash/dd Changelog register failed:
[Errno 111] Connection refused

10.70.42.75 - pre failed: [2015-05-22 16:26:00.321920] I
[event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with
index 3
/rhs/thinbrick1/nash/dd Changelog register failed: [Errno 111] Connection
refused

10.70.42.75 - pre failed: /rhs/thinbrick2/nash/dd Changelog register failed:
[Errno 111] Connection refused

Generated output file /tmp/out.txt
[root at dhcp43-140 ~]#


--- Additional comment from Aravinda VK on 2015-05-27 12:39:44 EDT ---

One more validation to glusterfind commands, Check Volume status before
executing create and pre commands.

XPath in volume info: volInfo/volumes/volume/statusStr

--- Additional comment from Aravinda VK on 2015-05-27 12:40:13 EDT ---

volInfo/volumes/volume/statusStr should be in Started state.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1223636
[Bug 1223636] 3.1 QE Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1224236
[Bug 1224236] [Backup]: RFE - Glusterfind CLI commands need to respond
based on volume's start/stop state
https://bugzilla.redhat.com/show_bug.cgi?id=1225564
[Bug 1225564] [Backup]: RFE - Glusterfind CLI commands need to respond
based on volume's start/stop state
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.