Bug 1317276 - Web interface don't start when not all host with storages is up [NEEDINFO]
Summary: Web interface don't start when not all host with storages is up
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.6.4
Hardware: x86_64
OS: Linux
unspecified
high vote
Target Milestone: ---
: ---
Assignee: Lev Veyde
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-13 17:29 UTC by Badalyan Vyacheslav
Modified: 2016-03-22 14:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-22 14:19:24 UTC
oVirt Team: Integration
ykaul: needinfo? (v.badalyan)
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
ScreenShots (476.00 KB, application/zip)
2016-03-13 17:29 UTC, Badalyan Vyacheslav
no flags Details

Description Badalyan Vyacheslav 2016-03-13 17:29:10 UTC
Created attachment 1135948 [details]
ScreenShots

Description of problem:
1. Have DC default (hosted engine).
2. Have 3 clusters. (one cluster it is two hosts with NFS for  hosted engine and only hosted engine VM active).
3. All host in clusters have local NFS share with storage domain
4. If ONE!! host is down - ovirt engine don't start web interface and don't start HA VMs. It's do forewer check!

Expected results:
1. Web interface will start
2. Storage domains and host will checks in backgroud like if engine allready was stared and one of hosts is down.


Why don't split datacenters? I was think to use clutser with hosted engine to start other VMs from domain.

If i down HP3 host - Engine Web UI don't start forever!

Comment 1 Yaniv Kaul 2016-03-13 21:16:55 UTC
What is 'local NFS share' ? Where's the NFS server?

Can you provide some logs?
What version is this?

Comment 2 Sandro Bonazzola 2016-03-22 14:19:24 UTC
Closing with insufficient data. If you can provide needed info, please reopen the bug.


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