Red Hat Bugzilla – Bug 808061
[RFE] virt-who command line option improvements
Last modified: 2013-01-08 02:35:37 EST
+++ This bug was initially created as a clone of Bug #808060 +++
Based on some usability discussions, we should enhance the cli command line options as follows.
Start in foreground, print errors to stderr (-d for debugging output)
2) virt-who -o
One-shot mode, exit after sending list of guests
3) virt-who -b
4) service virt-who start
Both the same: start on background (do double-fork), log to /var/log, no
It will be better to do a rebase, because this change affects quite big codebase. Other changes from upstream (couple of fixes that is already present in rhel-6) needs to be dragged as well, so rebase makes sense.
This feature has been implemented in virt-who-0.7-1.el5.
-b and -d options work well ,but some error happen to -o option as follows:
2012-08-01 23:27:40,303 [ERROR] @virt-who.py:164 - Unable to create connection:
Traceback (most recent call last):
File "/usr/share/virt-who/virt-who.py", line 161, in _send
File "/usr/share/virt-who/virt-who.py", line 140, in checkConnections
File "/usr/share/virt-who/virt-who.py", line 95, in initVirt
self.virt = Virt(self.logger)
File "/usr/share/virt-who/virt.py", line 41, in __init__
VirtError: adding cb to list
2012-08-01 23:27:40,310 [ERROR] @virt-who.py:167 - Unable to recover
Thanks for noticing, it has been fixed in virt-who-0.7-2.el5.
This issue will be as a tracker of the following bugs:
848763 848777 848781. After the all the bugs fixed, this bug will be closed.
Removing dependence on bug 808060, because it's RHEL-6 bug.
Dependent bugs are fixed, moving to ON_QA.
Since the virt-who with -o function works well without errors in virt-who-0.7-6.el5, changed status from ON_QA to VERIFIED.
The dependence bugs have been fixed. so moving the bug to Verified. Moreover, the virt-who with -o function works well without errors in virt-who-0.7-6.el5, changed status from ON_QA to 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.