Bug 1076530

Summary:	engine shouldn't kill the vds running the VM with the hosted engine
Product:	[oVirt] ovirt-engine	Reporter:	Jiri Moskovcak <jmoskovc>
Component:	General	Assignee:	Doron Fediuck <dfediuck>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, dfediuck, gklein, jmoskovc, lbednar, rbalakri, sbonazzo, yeylon
Target Milestone:	ovirt-3.6.0-ga	Keywords:	TestOnly, Triaged
Target Release:	3.6.0	Flags:	rule-engine: ovirt-3.6.0+ ylavi: planning_ack+ rule-engine: devel_ack+ mavital: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sla
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Cause: An old libvirt version might cause a host to be degraded to a lower cluster level. Consequence: Hosted engine installation might fail when host is being added to the engine as the host does not fit the required cluster level. Workaround (if any): Upgrade libvirt to the latest available version before starting hosted engine installation. Result: Hosted engine deployment passes successfully and adds the host to the engine.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-19 15:34:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Moskovcak 2014-03-14 13:51:21 UTC

Description of problem:
I've installed the the hosted engine setup (3.4rc2) and when I got to the point where the hosted-engine-setup tries to add the host running the VM with the engine to the cluster controlled by the engine, I got an error saying:

"Host hosted_engine_1 is compatible with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Default which is set
to version 3.4"

and then the host is marked as non operational which destroys the vm with the running engine

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.1.1-1.fc19.noarch
ovirt-engine-3.4.0-0.13.rc.fc19.noarch

How reproducible:
100%

Steps to Reproduce:
1. install host with older libvirt
2. install the engine using the ovirt-hosted-engine-install
3. watch the engine commit suicide when it kills it's own VM

Actual results:
engine marks the hosts as "non operational" which destroys the vm where the engine is running..

Expected results:
engine refuses to turn off the host which hosts the VM with the engine

Comment 1 Sandro Bonazzola 2014-05-08 13:55:27 UTC

This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.

Comment 4 Sandro Bonazzola 2015-09-04 08:59:15 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 5 Doron Fediuck 2015-10-07 06:15:08 UTC

Sandro,
is this bz still relevant?

Comment 6 Sandro Bonazzola 2015-10-07 08:23:06 UTC

I don't think so.
Right now both host and engine cluster level should be 3.6 so this shouldn't happen anymore.

Comment 7 Sandro Bonazzola 2015-10-07 08:23:48 UTC

Moving to QA Test only.

Comment 8 Nikolai Sednev 2015-12-08 10:23:26 UTC

Hi Jiri,
I'm not quite following the work flow. 
Why to install HE over unclean host with already installed libvirt on it?
For reproduction steps I'm required to install on host repositories of 3.4 and then install that host to 3.4 engine or to install outdated 3.4's libvirt on host and then to change repositories to 3.6 on host and install 3.6HE on host?
Please provide me with more detailed steps for reproduction.

Comment 9 Nikolai Sednev 2016-01-13 09:24:51 UTC

Hi Doron,
I see that within the reproduction steps it appears that environment is dirty, "1. install host with older libvirt". I performed several times HE deployments for the latest 3.6.2 and they all worked fine on clean environments.
Please consider closing this as not a bug.

Comment 10 Nikolai Sednev 2016-01-13 17:45:52 UTC

Works for me on these components:
HE-VM is running with these components:
rhevm-dwh-setup-3.6.2-1.el6ev.noarch
ovirt-vmconsole-1.0.0-1.el6ev.noarch
rhevm-dwh-3.6.2-1.el6ev.noarch
ovirt-engine-extension-aaa-jdbc-1.0.4-1.el6ev.noarch
rhevm-3.6.2-0.1.el6.noarch
ovirt-setup-lib-1.0.1-1.el6ev.noarch
ovirt-vmconsole-proxy-1.0.0-1.el6ev.noarch
ovirt-host-deploy-1.4.1-1.el6ev.noarch
ovirt-host-deploy-java-1.4.1-1.el6ev.noarch

Hosts:
mom-0.5.1-1.el7ev.noarch
ovirt-vmconsole-1.0.0-1.el7ev.noarch
ovirt-hosted-engine-ha-1.3.3.6-1.el7ev.noarch
qemu-kvm-rhev-2.3.0-31.el7_2.5.x86_64
ovirt-vmconsole-host-1.0.0-1.el7ev.noarch
ovirt-host-deploy-1.4.1-1.el7ev.noarch
libvirt-client-1.2.17-13.el7_2.2.x86_64
sanlock-3.2.4-2.el7_2.x86_64
ovirt-setup-lib-1.0.1-1.el7ev.noarch
vdsm-4.17.15-0.el7ev.noarch
ovirt-hosted-engine-setup-1.3.2.1-1.el7ev.noarch