Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 215638 - KeyError when trying to create a fully-virt domain with virt-manager
KeyError when trying to create a fully-virt domain with virt-manager
Status: CLOSED DUPLICATE of bug 220036
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Berrange
Depends On:
  Show dependency treegraph
Reported: 2006-11-14 18:01 EST by Chris Lalancette
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-05 09:07:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Lalancette 2006-11-14 18:01:17 EST
Description of problem:
I tried to create a fully-virtualized domain on x86_64 Xen (kernel
2.6.18-1.2747.el5xen).  After getting to the last screen and clicking on
"Finish", the "Creating Domain" dialog comes up for a few seconds, and then
disappears and drops me back at the last dialog.  On the console, I get the
following message:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 388, in finish
    vm = self.connection.get_vm(guest.uuid)
  File "/usr/share/virt-manager/virtManager/connection.py", line 60, in get_vm
    return self.vms[uuid]
KeyError: 'c845d431-23e6-60b7-7186-7cd2fdfdb392'

It would seem that connection.py is trying to access an array element that isn't
there, but since my knowledge of python is so limited, I won't speculate further
than that.

Version-Release number of selected component (if applicable):
virt-manager 0.2.5-1.el5
Comment 1 Daniel Berrange 2007-01-05 09:07:37 EST

*** This bug has been marked as a duplicate of 220036 ***

Note You need to log in before you can comment on or make changes to this bug.