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

[bugzilla at redhat.com]

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

            Bug ID: 1223206
           Summary: "Snap_scheduler disable" should have different return
                    codes for different failures.
           Product: Red Hat Gluster Storage
           Version: 3.0
         Component: gluster-snapshot
          Keywords: Triaged
          Severity: medium
          Assignee: rjoseph at redhat.com
          Reporter: asengupt at redhat.com
        QA Contact: storage-qa-internal at redhat.com
                CC: asengupt at redhat.com, bugs at gluster.org,
                    dnarayan at redhat.com, gluster-bugs at redhat.com
        Depends On: 1218055
            Blocks: 1186580 (qe_tracker_everglades)



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

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:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1218055
[Bug 1218055] "Snap_scheduler disable" should have different return codes
for different failures.
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LurSW7KkQP&a=cc_unsubscribe