Bug 1385401 - Can not start setup procedure
Summary: Can not start setup procedure
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 2.0.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Sandro Bonazzola
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-16 20:44 UTC by gregor
Modified: 2017-05-11 09:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-17 21:01:32 UTC
oVirt Team: Integration
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1001181 0 high CLOSED [RFE] Provide clean up script for complete cleaning the hosted engine VM installation after failed installation. 2021-02-22 00:41:40 UTC

Internal Links: 1001181

Description gregor 2016-10-16 20:44:24 UTC
Description of problem:
After a failed installation I removed all the ovirt and vdsm components, rebooted the machine and started from the beginning. Now the installation did not start because vdsm can't start.

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

Steps to Reproduce:
1. yum remove ovirt-* vdsm-* libvirt-* python-ovirt-engine-sdk4 postgresql-* qemu-*
2. reboot
3. yum -y install ovirt-hosted-engine-setup ovirt-engine-appliance guster-server vdsm-gluster
4. hosted-engine --deploy

Actual results:
The installer stucked at "[ INFO  ] Stage: Environment setup"

Expected results:
The installation should be possible

Additional info:
These are relevant lines from /var/log/vdsm/supervdsm.log

MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::69::blivet::(log_exception_info) IGNORED:        Caught exception, continuing.
MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::72::blivet::(log_exception_info) IGNORED:        Problem description: failed to get initiator name from iscsi firmware
MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::73::blivet::(log_exception_info) IGNORED:        Begin exception details.
MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::76::blivet::(log_exception_info) IGNORED:            Traceback (most recent call last):
MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::76::blivet::(log_exception_info) IGNORED:              File "/usr/lib/python2.7/site-packages/blivet/iscsi.py", line 142, in __init__
MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::76::blivet::(log_exception_info) IGNORED:                initiatorname = libiscsi.get_firmware_initiator_name()
MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::76::blivet::(log_exception_info) IGNORED:            IOError: Unknown error
MainThread::DEBUG::2016-10-16 22:42:26,944::storage_log::77::blivet::(log_exception_info) IGNORED:        End exception details.

Comment 1 Michal Skrivanek 2016-10-17 07:19:52 UTC
I suppose this is an incorrect cleanup. Simone?

Comment 2 Sandro Bonazzola 2016-10-17 07:27:56 UTC
Nir can you have a look at above traceback?

Gregor, can you please provide a sos report of the host?

Comment 3 Simone Tiraboschi 2016-10-17 07:56:45 UTC
(In reply to Michal Skrivanek from comment #1)
> I suppose this is an incorrect cleanup. Simone?

Yes, I think so.

Comment 4 gregor 2016-10-17 09:01:57 UTC
In the meantime I followed this instruction which did not help:

https://www.ovirt.org/documentation/how-to/hosted-engine/#recoving-from-failed-install

Is it save to upload the sosreport here? I read through this article: https://access.redhat.com/solutions/3592

Comment 5 gregor 2016-10-17 21:01:32 UTC
Because the server has to be finished and shipped to my customer I decided to reinstall the whole operating-system. 
This is a very bad solution but after 20 hours of try-and-error I have to find any solution.

Thanks for your help.


Note You need to log in before you can comment on or make changes to this bug.