[Bug 931133] New: virt-manager can no longer connect to libvirtd 0.9.12.3 over QEMU+SSH
http://bugzilla.opensuse.org/show_bug.cgi?id=931133 Bug ID: 931133 Summary: virt-manager can no longer connect to libvirtd 0.9.12.3 over QEMU+SSH Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: jrhodes@redpointsoftware.com.au QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Build Identifier: I have a remote machine running libvirtd which I used to connect to with virt-manager over SSH. Since upgrading virt-manager recently on Factory, it is no longer able to connect to the remote machine. Instead I get the following message: Error polling connection 'qemu+ssh://root@192.168.1.172/system': 0 Details: Error polling connection 'qemu+ssh://root@192.168.1.172/system': 0 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 358, in _handle_tick_queue conn.tick_from_engine(**kwargs) File "/usr/share/virt-manager/virtManager/connection.py", line 1266, in tick_from_engine raise e # pylint: disable=raising-bad-type KeyError: 0 Reproducible: Always Steps to Reproduce: 1. Open virt-manager 2. Connect to a remote machine over QEMU+SSH that is running libvirtd 0.9.12.3 3. Observe error Actual Results: virt-manager does not connect and fails with an error as detailed in the description Expected Results: virt-manager should connect correctly -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=931133 James Rhodes <jrhodes@redpointsoftware.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from James Rhodes <jrhodes@redpointsoftware.com.au> --- This appears to be fixed after performing "zypper up" today. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com