Bug 1078291

Summary: deployments take more than 60 seconds
Product: Red Hat Enterprise Virtualization Manager Reporter: Yedidyah Bar David <didi>
Component: ovirt-engine-setupAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: movciari
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: aberezin, alonbl, bazulay, didi, gklein, iheim, rbalakri, Rhev-m-bugs, sbonazzo, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: When using a remote db, ovirt-engine-dwh-setup used the same db host as the engine. Consequence: It was not possible to specify different db host. Fix: In 3.4, the dwh setup utility was replaced with a plugin to the common engine-setup utility, and this plugin query for all db credentials. It was not documented in 3.4 afaik, and considered to be a "tech preview". Result: It's now possible to input a db host as needed when setting up dwh with a remote db.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-12 14:15:42 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:
Bug Depends On:    
Bug Blocks: 1142923, 1156165    
Description Flags
server.log - failed after 60 seconds
server.log - succeeded after almost 2 minutes none

Description Yedidyah Bar David 2014-03-19 14:39:21 UTC
Description of problem:

I got in server.log this line:

2014-03-19 15:53:31,273 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

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

current nightly master on fully updated fedora 19


How reproducible:

Not sure

Steps to Reproduce:
1. install/setup engine+dwh+reports on a moderately-slow machine

Actual results:

Deployment fails

Expected results:

Should succeed

Additional info:

Increased the timeout to 10 minutes in [1], and it succeeds, took almost two minutes.

[1] http://gerrit.ovirt.org/25895

Comment 2 Yedidyah Bar David 2014-03-19 14:47:24 UTC
Created attachment 876371 [details]
server.log - failed after 60 seconds

Comment 3 Yedidyah Bar David 2014-03-19 14:48:12 UTC
Created attachment 876373 [details]
server.log - succeeded after almost 2 minutes

Comment 4 Yedidyah Bar David 2014-03-19 14:54:45 UTC
I now checked logs of a 3.3 engine and deployment there took 4.5 minutes and was not stopped. Perhaps the default timeout changed, or something else in jboss.

Comment 5 Alon Bar-Lev 2014-03-20 07:48:14 UTC
Why is it downstream bug?

Comment 6 Sandro Bonazzola 2014-04-03 12:38:48 UTC
(In reply to Alon Bar-Lev from comment #5)
> Why is it downstream bug?

JBoss is not changed upstream.

Comment 7 Sandro Bonazzola 2014-04-03 13:53:58 UTC
Patch merged upstream on master branch for 3.5.0 rebase.

Comment 10 movciari 2014-10-22 10:37:34 UTC
this was on fedora 19 which is not supported by rhevm, and also only on slow machine, which must be much slower than minimum hardware requirements for rhevm.
we use rhevm on rhel on very slow machines every day and it works

Comment 11 Yedidyah Bar David 2014-10-22 11:33:42 UTC
(In reply to movciari from comment #10)
> this was on fedora 19 which is not supported by rhevm,

Don't think that's relevant, what's relevant is version of jboss - not sure what's happening there on the various OSes etc.

> and also only on slow
> machine, which must be much slower than minimum hardware requirements for
> rhevm.

IIRC the minimum hardware requirements do not specifically mention IO, and in any case, IO is much less predictable/controllable than cpu/memory, and imo we definitely want to make sure we don't fail, especially considering that it was an easy fix.

> we use rhevm on rhel on very slow machines every day and it works

Which version? With this patch applied, which is true for most versions of the last half year, you have ten minutes to deploy.

If you want to reproduce, simply edit [1], change 'deployment-timeout="1200"' to something much lower, e.g. 'deployment-timeout="10"', and stop/start the engine.

[1] /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.xml.in

Comment 12 Yedidyah Bar David 2014-11-04 13:08:41 UTC
I do not think this requires doc text, as it did not affect, to the best of my knowledge, any released version.