Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: The "wallaby list-snapshots" utility exited with a failure status if no snapshots existed in the store. C: This behavior may have been confusing for some users. F: The "wallaby list-snapshots" does not exit with a failure status if it otherwise succeeds but finds no snapshots. R: Users should find that the exit-status behavior of the wallaby list-snapshots command is now more consistent with their expectations.
# wallaby list-snapshots Console Connection Established... # echo $? 1 # rpm -q wallaby wallaby-0.10.4-1.el5 >>> ASSIGNED
Tested with (version): wallaby-0.10.4-2 # wallaby list-snapshots Console Connection Established... # echo $? 0 Tested on: RHEL5 i386,x86_64 - passed >>> VERIFIED
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1 @@ -C: The "wallaby list-snapshots" utility exited with a failure status if no snapshots existed in the store. +Running "wallaby list-snapshots" resulted in a non-zero exit code, indicating failure, even when no snapshots existed in the store. With this update, the "wallaby list-snapshots" operation exits with an exit code of 0 (zero) if it does not find any snapshots, but otherwise succeeds, as expected.-C: This behavior may have been confusing for some users. -F: The "wallaby list-snapshots" does not exit with a failure status if it otherwise succeeds but finds no snapshots. -R: Users should find that the exit-status behavior of the wallaby list-snapshots command is now more consistent with their expectations.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0217.html