Bug 676676 - Rebooting a cluster node with KVM/qemu VMs configured, makes the VMs to cold boot and there is no way to live-migrate them by default
Summary: Rebooting a cluster node with KVM/qemu VMs configured, makes the VMs to cold ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rgmanager
Version: 6.3
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Filip Skola
URL:
Whiteboard:
Depends On: 575978
Blocks: 1159926 1172231
TreeView+ depends on / blocked
 
Reported: 2011-02-10 17:27 UTC by Shane Bradley
Modified: 2019-08-15 03:32 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 575978
Environment:
Last Closed: 2015-10-20 17:23:59 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 46250 0 None None None 2012-08-30 15:19:35 UTC

Comment 1 Shane Bradley 2011-02-10 17:28:52 UTC
This is clone of https://bugzilla.redhat.com/show_bug.cgi?id=575978 to have vm live migrated if node running vm service rgmanager is shutdown or rebooted.

Comment 6 RHEL Program Management 2011-06-13 17:05:04 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 19 Chris Williams 2015-10-20 17:23:59 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6 and therefore will be closed. 
This is a nice-to-have, but ultimately would require too much of a change to the rgmanager shutdown procedure to be included in rgmanager at this time as RHEL 6 begins it's transition to Production Phase 2. The goal for 6.8 will be stability so RFEs need to be very carefully considered and this RFE is too risky a change this late in the RHEL 6 life cycle. 
In a perfect world we'd be able to resolve every bug and implement every good RFE. Unfortunately, critical bug fixes have taken priority over this feature request.


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