[Bugs] [Bug 1218055] New: "Snap_scheduler disable" should have different return codes for different failures.

[bugzilla at redhat.com]

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

            Bug ID: 1218055
           Summary: "Snap_scheduler disable" should have different return
                    codes for different failures.
           Product: GlusterFS
           Version: 3.7.0
         Component: snapshot
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: dnarayan at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
Currently "snap_scheduler disable" command has same return code for different
types of failures like; snap_scheduler init not executed, snap_scheduler
already disabled.. etc. 
When this command is executed through an external program like vdsm, its better
to depend on return code than messages to recognise the failures. So, its
better to have different return codes for different errors. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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