Hide Forgot
Description of problem: --roots and --from are mutually exclusive options for virsh snapshot-list command, however, the programming just raises a error without exiting. Version-Release number of selected component (if applicable): # rpm -q libvirt-client libvirt-client-0.9.10-8.el6.x86_64 How reproducible: always Steps to Reproduce: # virsh list Id Name State ---------------------------------------------------- 14 foo running 1. # virsh snapshot-create-as foo --name "hello" Domain snapshot hello created # virsh snapshot-create-as foo --name "libvirt" Domain snapshot libvirt created Notes, in order to show some details, I created a 'libvirt' child snapshot based on 'hello' snapsthot, in fact, it's not necessary. 2. # virsh snapshot-list foo --roots --from "hello" error: --roots and --from are mutually exclusive Name Creation Time State ------------------------------------------------------------ libvirt 2012-03-28 13:46:51 +0800 running Actual results: error: --roots and --from are mutually exclusive Name Creation Time State ------------------------------------------------------------ libvirt 2012-03-28 13:46:51 +0800 running Expected results: The programming should be terminated when meeting a error. Additional info:
Patch for upstream: https://www.redhat.com/archives/libvir-list/2012-March/msg01235.html
Alex, is this virsh only or does it affect any user of the api?
(In reply to comment #2) > Alex, is this virsh only or does it affect any user of the api? Hello Dave, It's a virsh layer bug and hasn't effect on a API, so don't worry about it. Alex
In POST: http://www.redhat.com/archives/libvir-list/2012-March/msg01242.html
Commit 03ca3317a66b7ae5a1a6323487cad99b506cb714 upstream, Daniel
Verify this bug with : libvirt-0.10.0-0rc0.el6.x86_64 1) perpare a domain with snapshot 2) run --roots --from snapshot-list # virsh snapshot-list ga --roots --from "hello" error: --roots and --from are mutually exclusive
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0276.html