Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1632242

Summary:

[RHV] VM on gluster storage domain can't be migrated

Product:

Red Hat Enterprise Virtualization Manager

Reporter:

SATHEESARAN <sasundar>

Component:

ovirt-hosted-engine-ha

Assignee:

Simone Tiraboschi <stirabos>

Status:

CLOSED DUPLICATE

QA Contact:

Pavel Stehlik <pstehlik>

Severity:

urgent

Docs Contact:

Priority:

unspecified

Version:

4.2.7

CC:

lsurette, rhs-bugs, sabose, sankarshan, ylavi

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

1632240

Environment:

Last Closed:

2018-10-08 07:54:48 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

Integration

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
vdsm.log file from the source host	none

Description SATHEESARAN 2018-09-24 12:33:06 UTC

+++ This bug was initially created as a clone of Bug #1632240 +++

Description of problem:
-----------------------
Unable to migrate HE VM to other hosts in the cluster

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHHI 2.0 - RHV 4.2.7 based on RHEL 7.6

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create a Hosted Engine setup with 3 hosts, with hosted engine image storage on gluster 3 way replica
2. Create a separate logical network, configure the network role - as migration network and gluster
3. All the hosts are capable of running hosted engine. ( hosted-engine --deploy done from RHV Manager UI, while adding the host )
4. Migrate the HE VM to other host

Actual results:
----------------
HE VM fails to migrate

Expected results:
-----------------
HE VM should be capable of migrating to other hosts

Comment 1 SATHEESARAN 2018-09-24 12:34:27 UTC

here is the snip from vdsm.log from the source host

<snip>
2018-09-24 16:01:57,374+0530 ERROR (migsrc/6c4b5577) [virt.vm] (vmId='6c4b5577-6d2d-49fb-a5d3-2cc541301b07') Unsafe migration: Migration without shared storage is unsafe (migration:290)
2018-09-24 16:01:57,719+0530 ERROR (migsrc/6c4b5577) [virt.vm] (vmId='6c4b5577-6d2d-49fb-a5d3-2cc541301b07') Failed to migrate (migration:455)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 437, in _regular_run
    self._startUnderlyingMigration(time.time())
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 509, in _startUnderlyingMigration
    self._perform_with_conv_schedule(duri, muri)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 587, in _perform_with_conv_schedule
    self._perform_migration(duri, muri)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 529, in _perform_migration
    self._migration_flags)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1779, in migrateToURI3
    if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self)
libvirtError: Unsafe migration: Migration without shared storage is unsafe
</snip>

Comment 2 SATHEESARAN 2018-09-24 12:36:03 UTC

Created attachment 1486388 [details]
vdsm.log file from the source host

Comment 3 SATHEESARAN 2018-09-26 10:42:53 UTC

This issue is seen with RHEL 7.6 with the following components:
qemu-kvm-rhev-2.12.0-16.el7.x86_64
libvirt-4.5.0-9.el7.x86_64

Comment 4 Sandro Bonazzola 2018-10-08 07:54:48 UTC

Closing as duplicate of bug #1632711

*** This bug has been marked as a duplicate of bug 1632711 ***