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

Bug 1184129

Summary:	migration to additional host fails before restarting HA agent
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-hosted-engine-setup	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED ERRATA	QA Contact:	Nikolai Sednev <nsednev>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	alukiano, didi, ecohen, iheim, juwu, lsurette, mavital, nsednev, pstehlik, sbonazzo, sherold
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	3.5.0-1	Flags:	juwu: needinfo-
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:	ovirt-hosted-engine-setup-1.2.1-9.el6ev	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1178535	Environment:
Last Closed:	2015-02-16 14:40:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1178535
Bug Blocks:

Comment 2 Nikolai Sednev 2015-01-21 15:16:00 UTC

Works for me on these components:
I've added RHEL7.0 host to my setup of two RHEL6.5 hosts after upgraded to latest vt from latest av, both RHEL6.5 hosts were upgraded to 6.6 and later added RHEL7.0 host to another host cluster, as RHEL7.0 can't be active with RHEL6.6 hosts within the same host cluster, then I've migrated my running RHEL6.5 VM from RHEL6.6 host cluster to RHEL7.0 host cluster, all without any problems.

RHEL7.0 host's components:
vdsm-4.16.8.1-6.el7ev.x86_64
sanlock-3.1.0-2.el7.x86_64
mom-0.4.1-4.el7ev.noarch
ovirt-hosted-engine-ha-1.2.4-5.el7ev.noarch
ovirt-host-deploy-1.3.0-2.el7ev.noarch
qemu-kvm-rhev-1.5.3-60.el7_0.11.x86_64
libvirt-client-1.1.1-29.el7_0.4.x86_64
ovirt-hosted-engine-setup-1.2.1-9.el7ev.noarch

RHEL6.0 host's components:
sanlock-2.8-1.el6.x86_64
libvirt-client-0.10.2-46.el6_6.2.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
mom-0.4.1-4.el6ev.noarch
vdsm-4.16.8.1-6.el6ev.x86_64
ovirt-hosted-engine-setup-1.2.1-9.el6ev.noarch
ovirt-host-deploy-1.3.0-2.el6ev.noarch
ovirt-hosted-engine-ha-1.2.4-5.el6ev.noarch

Engine:
rhevm-3.5.0-0.30.el6ev.noarch
rhevm-guest-agent-common-1.0.10-2.el6ev.noarch

Comment 3 Yedidyah Bar David 2015-01-21 15:19:25 UTC

(In reply to Nikolai Sednev from comment #2)
> Works for me on these components:
> I've added RHEL7.0 host to my setup of two RHEL6.5 hosts after upgraded to
> latest vt from latest av, both RHEL6.5 hosts were upgraded to 6.6 and later
> added RHEL7.0 host to another host cluster, as RHEL7.0 can't be active with
> RHEL6.6 hosts within the same host cluster, then I've migrated my running
> RHEL6.5 VM

The engine VM? I didn't even know this works/supported :-)

> from RHEL6.6 host cluster to RHEL7.0 host cluster, all without
> any problems.

Comment 4 Yedidyah Bar David 2015-02-02 06:54:41 UTC

Julie,

I understand that you set doc text to '-' because I did so for the 3.6 bug. Sorry for not doing that myself.

The bug did not affect 3.4, so only users upgrading to 3.5.0 and not to 3.5.0-1 will be affected.

However, there is a user-visible (and affecting) change in the fix - we use now the hostname and not the IP address of each host. See the 3.6 bug 1178535 comment 9. So you might want to document this somewhere, perhaps in the main documentation. Please see there also comments 10 and 17.

Thanks.

Comment 6 errata-xmlrpc 2015-02-16 14:40:25 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-2015-0229.html