Bug 454620
| Summary: | Could not refresh connection xen:/// exceptions.KeyError '00000000-0000-0000-0000-000000000000' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Alexander Todorov <atodorov> | ||||
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 5.2 | CC: | xen-maint | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-01-23 15:59:22 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Alexander Todorov
2008-07-09 12:55:07 UTC
Created attachment 311369 [details]
virt-manager.log with the 2 error messages
Please advise if the 2 error messages are related to each other or they need separate bugs. Thanks! This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Okay, the gist here is that something in the xen/libvirt arena is out of whack after you destroy the guest (that is the 'internal error domain information incomplete, missing name' error). As a result, we get cascading errors from virt-manager which aren't the root issue (that's the KeyError 000... part). Alexander, can you still reproduce this on rhel 5.3? If so, can you post: virsh dumpxml vmname xm list --long vmname Both before the failure and after the failure? If you can't reproduce, my assumption is that the underlying bug was fixed for 5.3 and we should close this. Could not reproduce on fresh 5.3 install with xen-3.0.3-80.el5, virt-manager-0.5.3-10.el5. Thanks, closing this as WORKSFORME. |