Bug 788132 - virt-manager does not show VMs
Summary: virt-manager does not show VMs
Keywords:
Status: CLOSED DUPLICATE of bug 786672
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: alpha
: 6.3
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-07 15:07 UTC by David Jaša
Modified: 2012-02-07 15:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 15:18:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Jaša 2012-02-07 15:07:05 UTC 
Description of problem:
when connected to the same host (RHEL 6.3), virt-managers shows empty list of VMs in some circumstances

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-8.el6.x86_64
python-2.6.6-29.el6.x86_64

How reproducible:


Steps to Reproduce:
1. run virt-manager --debug
2. connect to the hypervisor
3.
  
Actual results:
virt-manager prints to log stuff like this:
2012-02-07 16:04:15,959 (cli:85): Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/manager.py", line 683, in vm_added
    self._append_vm(model, vm, conn)
  File "/usr/share/virt-manager/virtManager/manager.py", line 754, in _append_vm
    row = self._build_vm_row(vm)
  File "/usr/share/virt-manager/virtManager/manager.py", line 736, in _build_vm_row
    row.insert(ROW_HINT, util.xml_escape(vm.get_description()))
  File "/usr/lib/python2.6/site-packages/virtinst/util.py", line 278, in xml_escape
    str = str.replace("&", "&")
AttributeError: 'NoneType' object has no attribute 'replace'


Expected results:
there are no tracebacks and list of VMs is shown

Additional info:
Comment 1 Cole Robinson 2012-02-07 15:18:24 UTC 

*** This bug has been marked as a duplicate of bug 786672 ***
Note You need to log in before you can comment on or make changes to this bug.