Red Hat Bugzilla – Bug 832071
Rgmanager and libvirt updates race condition
Last modified: 2012-08-17 14:35:59 EDT
Description of problem:
Libvirt was updated yesterday to version 0.9.4-23.el6_2.9. While
updating libvirt, virsh command is unavailable to rgmanager leading one node to stop two guests services:
Jun 13 15:01:12 kvm2 rgmanager: [vm] Cannot find 'virsh'; is it installed?
Jun 13 15:01:12 kvm2 rgmanager: status on vm "kvm2_cups_x86_64_RHEL5" returned 2 (invalid argument(s))
Jun 13 15:01:12 kvm2 rgmanager: [vm] Could not determine Hypervisor
Jun 13 15:01:12 kvm2 rgmanager: status on vm "kvm2_sam_x86_64_RHEL5" returned 2 (invalid argument(s))
Jun 13 15:01:12 kvm2 rgmanager: Stopping service vm:kvm2_cups_x86_64_RHEL5
Jun 13 15:01:12 kvm2 rgmanager: Stopping service vm:kvm2_sam_x86_64_RHEL5
Jun 13 15:01:14 kvm2 yum: Updated: libvirt-client-0.9.4-23.el6_2.9.x86_64
Jun 13 15:01:14 kvm2 yum: Updated: libvirt-python-0.9.4-23.el6_2.9.x86_64
Jun 13 15:01:20 kvm2 yum: Updated: libvirt-0.9.4-23.el6_2.9.x86_64
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.2 (Santiago)
While libvirt updates are installed with yum update. Behavior
observed on only one node, the other node was not affected by
updating libvirt. Maybe a rare race condition.
Steps to Reproduce:
1. yum update
Guests may crash and rgmanager stops vm service
Guests should'nt be affected by updating libvirt
The update of libvirt would have to occur at the same time as a status check; so this should not be common.
This can be worked around by interacting with rgmanager in a couple of ways, the most obvious is to 'freeze' all services on a host, upgrade libvirt, then unfreeze all services.
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.