Bug 1317277

Summary: Web interface don't start when not all host with storages is up
Product: [oVirt] ovirt-engine Reporter: Badalyan Vyacheslav <v.badalyan>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.4CC: bugs, michal.skrivanek, tjelinek, v.badalyan
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-13 06:50:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ScreenShots none

Description Badalyan Vyacheslav 2016-03-13 17:29:39 UTC
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 Badalyan Vyacheslav 2016-03-13 17:29:56 UTC
Created attachment 1135949 [details]
ScreenShots

Comment 2 Michal Skrivanek 2016-03-14 07:51:12 UTC
I don't really follow the issue. Which host is down in step 4? The one running hosted engine VM?
Or a different host in other cluster?
"don't start web interface" - you mean the management UI is not available as the engine is actually not running?

Comment 3 Tomas Jelinek 2016-03-14 08:44:55 UTC
@Badalyan also please attach all the logs (engine.log and ui.log)

Comment 4 Tomas Jelinek 2016-03-23 11:11:19 UTC
@Badalyan - does this still happen to you? If yes, could you please provide the info asked above?

Comment 5 Tomas Jelinek 2016-04-13 06:50:31 UTC
We don't have enough information on what has happened. Closing this issue - if it still happens, please feel free to reopen and add all the info requested.

Comment 6 Red Hat Bugzilla 2023-09-14 03:19:21 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days