Red Hat Bugzilla – Bug 839930
There is no message if debug level number is out of scope when run a virsh command with -d option
Last modified: 2013-08-04 23:43:39 EDT
Description of problem:
There is no message if debug level number is out of scope when run a virsh command with -d option.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make sure there is a storage pool.
2. Run #virsh -d 10000 pool-start $poolname.
3. Run #virsh -d -10000 pool-start $poolname.
1. Command 2 and 3 can work normally without any messages.
1. At least, there should be some warning messages said the debug level is out of scope. Normally, debug level should be in 0-4.
1. Steps in this bug is just a example, this issue can be reproduced by all virsh commands with -d option.
Upstream patch proposed
Fixed by commit 4fedf388f68b49dd1a8334f75272c3bfddd6032c
virsh: check if specified debug level is in range
Test it with libvirt-0.10.0-0rc0.el6
# virsh -d 1000 pool-destroy default
error: ignoring debug level 1000 out of range [0-4]
Pool default destroyed
So it's verified
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.