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 1285921 - Can't migrate VMs with cache != none, but 'none' doesn't work with 4k native drives
Summary: Can't migrate VMs with cache != none, but 'none' doesn't work with 4k native ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: resource-agents
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-27 00:46 UTC by Madison Kelly
Modified: 2016-05-10 19:15 UTC (History)
4 users (show)

Fixed In Version: resource-agents-3.9.5-30.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 19:15:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0735 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2016-05-10 22:28:24 UTC

Description Madison Kelly 2015-11-27 00:46:48 UTC 
Description of problem:

Systems with 4k native disks are not compatible with 'cache=none' (install fails, it can't see the disk). So cache must be set to 'writeback' or 'writethrough'. However, with this set, migration fails:

====
[root@node2 ~]# clusvcadm -M vm:server -m node2.ccrs.bcn
Trying to migrate vm:server to node2.ccrs.bcn...Failed; service running on original owner
====

Logs on host:

====
Nov 27 02:41:06 node1 rgmanager[32465]: Migrating vm:server to node2.ccrs.bcn
Nov 27 02:41:06 node1 rgmanager[684]: [vm] Migrate server to node2.ccrs.bcn failed:
Nov 27 02:41:06 node1 rgmanager[706]: [vm] error: Unsafe migration: Migration may lead to data corruption if disks use cache != none
Nov 27 02:41:06 node1 rgmanager[32465]: migrate on vm "server" returned 150 (unspecified)
Nov 27 02:41:06 node1 rgmanager[32465]: Migration of vm:server to node2.ccrs.bcn failed; return code 150
====


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

resource-agents-3.9.5-24.el6_7.1.x86_64



How reproducible:

100%


Steps to Reproduce:
1. Build a machine using only 4k native drives
2. Create a VM with a dedicated clustered LV as storage, verify that 'cache=none' is not supported.
3. Use 'cache=write{back,through}', confirm VM now installs.
4. Try to migrate the VM.


Actual results:

Refuses to migrate


Expected results:

Migrate, though possibly with warning or alert of some sort. Possibly call a flush after pausing the VM prior to kicking over to the peer?


Additional info:

Using a cman + rgmanager cluster.
Comment 2 Oyvind Albrigtsen 2015-11-30 16:27:14 UTC 
Tested and created pull request for working patch: https://github.com/ClusterLabs/resource-agents/pull/707
Comment 3 Oyvind Albrigtsen 2015-11-30 16:31:35 UTC 
Set migrate_options="--unsafe" to make it work where cache!=none.
Comment 4 Madison Kelly 2015-11-30 16:36:55 UTC 
I will grab a copy of the patched RA and test in the next day or two and report back.

Thanks!
Comment 5 Oyvind Albrigtsen 2016-01-08 09:09:56 UTC 
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
Comment 7 Madison Kelly 2016-01-22 00:12:59 UTC 
This appears to now work. Thank you!
Comment 10 errata-xmlrpc 2016-05-10 19:15:33 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.