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

Bug 1070052

Summary: hosted-engine --vm-start doesn't start the VM even though the VM is down.
Product: Red Hat Enterprise Virtualization Manager Reporter: Chen <cchen>
Component: ovirt-hosted-engine-setupAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED DUPLICATE QA Contact: Leonid Natapov <lnatapov>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.0CC: gklein, iheim
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-27 11:11:20 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 Chen 2014-02-26 07:24:11 UTC
Description of problem:

hosted-engine --vm-start doesn't start the VM even though the VM is down.

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

ovirt-hosted-engine-setup-1.0.0.4

How reproducible:

Always

Steps to Reproduce:

1. Use remote-viewer vnc://localhost:5900 to open a console

2. Poweroff the VM in the console

3. Can not start the VM via hosted-engine --vm-start. The output is

Virtual machine already exists.

Actual results:

The VM doesn't start.

Expected results:

The VM should start.

Workaround:

Use hosted-engine --vm-poweroff to first poweroff the VM and then use hosted-engine to start the VM.

Additional info:

Comment 1 Sandro Bonazzola 2014-02-27 11:11:20 UTC
(In reply to Chen from comment #0)
> Description of problem:
> 
> hosted-engine --vm-start doesn't start the VM even though the VM is down.
> 
> Version-Release number of selected component (if applicable):
> 
> ovirt-hosted-engine-setup-1.0.0.4

It has been already fixed in ovirt-hosted-engine-setup-1.0.0-6.

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