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

Bug 1055059

Summary:	The --vm-start function does not call the createvm command but --vm-start-paused does
Product:	[Retired] oVirt	Reporter:	Andrew Lau <andrew>
Component:	ovirt-hosted-engine-setup	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	movciari
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.4	CC:	acathrow, didi, fw, gklein, iheim, sbonazzo, talayan, yeylon
Target Milestone:	---
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	ovirt-3.4.0-beta2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-31 12:29:41 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 Andrew Lau 2014-01-18 13:03:50 UTC

Description of problem:
After the engine has been installed and the pass off to the HA services happens the VM is not brought back online. 

Running the command `hosted-engine --vm-start` will not call the createvm command in VDSM and fail with no status.

VDSM Logs: http://www.fpaste.org/69592/00427141/
ovirt-hosted-engine-ha agent.log http://www.fpaste.org/69595/43609139/

However, the workaround of starting the vm in paused state seems to run the createvm command.

`hosted-engine --vm-start-paused`

This seems to create the VM, which I was then able to resume by using `virsh resume HostedEngine`

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-ha-1.1.0-0.0.master.20140116.git3db8f76.el6.noarch
ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch
vdsm-4.14.0-29.git6c6da59.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install hosted-engine as per normal
2. Power off/Reboot VM after the engine has been installed and is to be passed off to the HA services
3. Try to start the VM using `hosted-engine --vm-start'

Actual results:
Engine VM is not started as the createvm is not called.

Expected results:
The Engine VM should start

Additional info:
The current workaround of starting in paused mode seems to be working.

Comment 1 Andrew Lau 2014-01-20 05:11:12 UTC

Interesting thing to note:

After it had booted once from the paused state method as mentioned above I brought it down and then backup normally with --vm-start and it seems to work.

Comment 2 Andrew Lau 2014-01-20 10:10:11 UTC

(In reply to Andrew Lau from comment #1)
> Interesting thing to note:
> 
> After it had booted once from the paused state method as mentioned above I
> brought it down and then backup normally with --vm-start and it seems to
> work.

Ignore this, I can't seem to be able to reproduce this. It must've happened during the transition period of the shutdown.

Comment 3 Frank Wall 2014-01-24 13:09:44 UTC

I had the exact same problem. After running hosted-engine --deploy successfully the hosted-engine VM could not be startet. In vdsm.log the error was 'Virtual machine does not exist'.

Following Andrew's hint and running `hosted-engine --vm-start-paused` and afterwards `virsh resume HostedEngine` the VM suddenly came up.

Then I initiated a VM shutdown through virsh and run `hosted-engine --vm-start` which succeeded.

Comment 4 Sandro Bonazzola 2014-02-07 11:19:59 UTC

Fixes should be in ovirt-3.4.0-beta2. Assignee please check.

Comment 5 Yedidyah Bar David 2014-02-09 11:37:25 UTC

Verified in ovirt-hosted-engine-setup-1.1.0-0.5.beta2.fc19.noarch from ovirt-3.4.0-prerelease .

Comment 6 Sandro Bonazzola 2014-03-31 12:29:41 UTC

this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released