RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 810576 - virt-manager doesn't survive transient libvirt outages
Summary: virt-manager doesn't survive transient libvirt outages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: virt-mgr-maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 884739 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-06 20:14 UTC by Michael Hines
Modified: 2014-04-10 08:16 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-10 08:16:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
example reconnect patch to /usr/share/virt-manager/virtManager/connection.py (1.53 KB, application/octet-stream)
2012-04-06 20:14 UTC, Michael Hines 		no flags Details
View All

Description Michael Hines 2012-04-06 20:14:25 UTC 
Created attachment 575819 [details]
example reconnect patch to /usr/share/virt-manager/virtManager/connection.py

Description of problem:
We had a group of machines with faulty hardware (of various kinds) which would cause the hypervisors to become unavailable for periods of seconds. (Very infrequent).

However, virt-manager would throw away all the libvirt connections and show "disconnected" even though the machines would come back to life a few seconds or minutes later....

A simple patch to /usr/share/virt-manager/virtManager.py solved the problem for us, but it would be nice to have this fixed in the future.

As it stands, when virt-manager detects a connection error, it just gives up until the user re-clicks the connection and instructs virt manager to attempt to reconnect again.

Shouldn't virt-manager auto-reconnect or at least *try* to auto-reconnect and then give up later?

I've attached a (crude) patch that fixed the problem for us, but such functionality could be generalized to any kind of transient problem in which the libvirt daemon became unavailable but was not permanently dead.

Version-Release number of selected component (if applicable):

Any version.

How reproducible:
100% reproducible.

Steps to Reproduce:
1. start virt manager
2. login to hypervisor and 'service libvirtd restart'
  
Actual results:
Virt-manager reports disconnected.


Expected results:
Virt-manager would attempt to reconnect a few times and give up later.


Additional info:
Comment 2 Cole Robinson 2012-04-16 14:32:07 UTC 
Not a bad idea in principle. Not that virt-manager should be patched to support crappy hardware, but I think the common case here is when libvirtd is restarted.

That patch isn't exhaustive enough though, and I'm hesitant to introduce a change like this at this point in the 6.3 cycle. Deferring to 6.4
Comment 3 Michael Hines 2012-04-16 14:37:55 UTC 
Thanks.

Yeah, there's no hurry. I fully expected the example patch to be completely replaced by somebody else. The quick patch I wrote just solved my immediate needs.
Comment 5 RHEL Program Management 2012-07-10 08:44:01 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 6 RHEL Program Management 2012-07-11 01:56:41 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 8 Dave Allan 2013-04-09 02:22:35 UTC 
*** Bug 884739 has been marked as a duplicate of this bug. ***
Comment 9 Martin Kletzander 2013-04-23 10:12:05 UTC 
The patch should definitely be more accurate, but as you said, this is really wanted feature and I think it would be very nice to have.  But since this isn't as big deal as various bug, we cannot give it full priority.  I'll have a look at it in the future.
Comment 10 RHEL Program Management 2014-04-10 08:16:58 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.