Bug 505340
| Summary: | VM migration and subsequent cluster.conf update can cause the VM restart | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Lon Hohberger <lhh> | ||||
| Component: | rgmanager | Assignee: | Lon Hohberger <lhh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 5.4 | CC: | cfeist, cluster-maint, cward, djansa, edamato, samuel.kielek, sghosh, tao | ||||
| Target Milestone: | rc | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rgmanager-2.0.51-1.el5 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-09-02 11:03:46 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 505479 | ||||||
| Attachments: |
|
||||||
|
Description
Lon Hohberger
2009-06-11 14:56:35 UTC
Created attachment 347426 [details]
Fix
* Ensures we use RG_STATUS_INQUIRY when determining if migration has completed,
* Ensures that subsequent RG_STATUS checks clear any NEEDSTOP flags to prevent this from happening in the future, and
* Fixes erroneous migration_mapping noise
I have reproduced this problem. The patch above worked for me. I tested by: * Creating a faux VM service, * Starting migrating it and ensuring that the actual migration for my fake VM service took >5 minutes. * After migration completed, I updated cluster.conf As expected, without the patch, the VM was restarted. With the patch, the update to cluster.conf did not cause a VM restart. Additionally, I tested standard service failure (by creating a service with an IP address and removing the IP address forcefully) to ensure the patch did not break normal service recovery. RHEL5 branch: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=47f11a83f75e8b6ea332dc64bf74bce793b0388e RHEL54 branch: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=1d101c6b92cad6266d41ad935e2dc8e1d06d732d I also tested: * Begin migrating faux VM service * Update cluster.conf with new config version -before- migration completes Note that users should not update configurations of services of virtual machines while they are in transition. ~~ Attention - RHEL 5.4 Beta Released! ~~ RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner! If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value. Questions can be posted to this bug or your customer or partner representative. For updating cluster.conf, all I did was (literally) change the config version and run 'ccs_tool update'. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1339.html |