Bug 1404241 - hoseted-engnie --deploy always fail if the fist attempt failed
Summary: hoseted-engnie --deploy always fail if the fist attempt failed
Keywords:
Status: CLOSED DUPLICATE of bug 1001181
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Simone Tiraboschi
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 13:04 UTC by Roman Hodain
Modified: 2017-05-11 09:26 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-13 13:25:21 UTC
oVirt Team: Integration
Embargoed:
rhodain: planning_ack?
rhodain: devel_ack?
rhodain: testing_ack?

Attachments (Terms of Use)
First attempt which triggered the issue (437.79 KB, text/plain)
2016-12-13 13:12 UTC, Roman Hodain 		no flags Details
Second attemp which always fails (170.33 KB, text/plain)
2016-12-13 13:14 UTC, Roman Hodain 		no flags Details
View All

Description Roman Hodain 2016-12-13 13:04:28 UTC 
Description of problem:
If the hosted engine deploy fails during the engine configuration, the deployment cannot be run again as it always fail.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-2.1.0-0.0.master.20161130101611.gitb3ad261.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1.run hosted-engine --deploy
2.Choose to automatically run engine-setup
3.Make sure that engine setup will fail

Actual results:
Another attempt to run the deployment fails

Expected results:
Another attempt can be triggered.

Additional info:
The second attempt fails with the following error:

[ ERROR ] The following VMs have been found: 2ee22064-36be-4a7a-b429-1889a23040e7
[ ERROR ] Failed to execute stage 'Environment setup': Cannot setup Hosted Engine with other VMs running
Comment 1 Roman Hodain 2016-12-13 13:12:37 UTC 
Created attachment 1231193 [details]
First attempt which triggered the issue
Comment 2 Roman Hodain 2016-12-13 13:14:51 UTC 
Created attachment 1231195 [details]
Second attemp which always fails
Comment 3 Roman Hodain 2016-12-13 13:18:06 UTC 
The uploaded logs are hosted engine setup logs.

The problem is that hosted-engine or vdsm does not properly cleaning the data and the VM recovery file remains in the ENV.

# ls -ld /var/run/vdsm/*-*
drwxr-xr-x. 2 vdsm kvm   40 Dec 13 13:43 /var/run/vdsm/2ee22064-36be-4a7a-b429-1889a23040e7
-rw-------. 1 vdsm kvm 5387 Dec 13 13:43 /var/run/vdsm/2ee22064-36be-4a7a-b429-1889a23040e7.recovery
Comment 4 Roman Hodain 2016-12-13 13:18:44 UTC 
Workaround is remove these files and restart vdsmd
Comment 5 Simone Tiraboschi 2016-12-13 13:25:21 UTC 
you could also simply run:
  hosted-engine --vm-poweroff

*** This bug has been marked as a duplicate of bug 1001181 ***
Note You need to log in before you can comment on or make changes to this bug.