Bug 1285921
Summary: | Can't migrate VMs with cache != none, but 'none' doesn't work with 4k native drives | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Madison Kelly <mkelly> |
Component: | resource-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.7 | CC: | agk, cluster-maint, djansa, fdinitto |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | resource-agents-3.9.5-30.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-10 19:15:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Madison Kelly
2015-11-27 00:46:48 UTC
Tested and created pull request for working patch: https://github.com/ClusterLabs/resource-agents/pull/707 Set migrate_options="--unsafe" to make it work where cache!=none. I will grab a copy of the patched RA and test in the next day or two and report back. Thanks! Before: # rpm -q resource-agents resource-agents-3.9.5-24.el6_7.1.x86_64 # clusvcadm -M vm:vm1 -m host2 Trying to migrate vm:vm1 to host2...Failed; service running on original owner # tail -f /var/log/cluster/rgmanager.log [vm] error: Unsafe migration: Migration may lead to data corruption if disks use cache != none After: Add migrate_options="--unsafe" to cluster.conf and reload the configuration. # rpm -q resource-agents resource-agents-3.9.5-30.el6.x86_64 # clusvcadm -M vm:vm1 -m host2 Trying to migrate vm:vm1 to host2...Success # tail -f /var/log/cluster/rgmanager.log [vm] virsh migrate --live --unsafe vm1 qemu+ssh://host2/system tcp:host2 Migration of vm:vm1 to host2 completed This appears to now work. Thank you! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0735.html |