Red Hat Bugzilla – Bug 474382
virt-manager returns "KeyError: 00000000-0000-0000-0000-000000000000"
Last modified: 2009-12-14 16:17:04 EST
Created attachment 325550 [details]
virt-manager.log of failure
Description of problem:
Attempting to bring up "Details" screen from virt-manager on Dom-0 fails on RHEL 5.2. Works on RHEL5.1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install fresh virgin copy of RHEL 5.2
2. Invoke virt-manager as root
3. Open connection to "Local"
4. Select "Domain-0"
5. Click on "Details" button
Selected item flashes, but no window opens. Error (see attached) appears in /root/.virtmanager/virt-manager.log
The "Details" window would open.
This does not occur in RHEL 5.1. In 5.1 the Details window opens. This failure occurs on both a fresh 5.2 install and on an upgraded 5.1 system. Note also that the "New" button is always disabled (grayed out) in 5.2.
The virt-manager.log from a fresh install of 5.2 is attached.
The hardware is HP DL380 G5
Problem occurs because 2 vmmConnection objects are created. The first with uri of "xen:///" and the other with an original uri of "xen". Even though the uri is changed from "xen" to "xen:///" change during the creation of the second object, it is a different object. Thus when Domain-0 is added it is added to the first object. However when selecting the Domain-0 on the window, the second object is selected by the "Details" button. Since the second object does not have Domain-0 in it, we get the KeyError. The root cause is the attempt to create the second object with the wrong uri.
Patch for virt-manager-0.5.3-8.el5 is attached. It is the same code that shows up in virt-manager-0.5.4.
Created attachment 325747 [details]
Fix for connect.py and connection.py
The change to connection.py was to eliminate a bandaid that was applied to hide the effect of the problem in connect.py. With only the connection.py patch, then two different rows for ID "xen" showed up - cooresponding to the two vmmConnection objects. One was Disconnected and the other Active.
Hi, thanks for the patch! Unfortunately for your patch's sake, we had another bug for this same issue, and it was fixed in 5.3 (bug 441850). So updating to the current release.
Closing as CURRENTRELEASE.