Bug 1078291
| Summary: | deployments take more than 60 seconds | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yedidyah Bar David <didi> | ||||||
| Component: | ovirt-engine-setup | Assignee: | Yedidyah Bar David <didi> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | movciari | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.5.0 | CC: | 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: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1142923, 1156165 | ||||||||
| Attachments: |
|
||||||||
|
Description
Yedidyah Bar David
2014-03-19 14:39:21 UTC
Created attachment 876371 [details]
server.log - failed after 60 seconds
Created attachment 876373 [details]
server.log - succeeded after almost 2 minutes
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. Why is it downstream bug? (In reply to Alon Bar-Lev from comment #5) > Why is it downstream bug? JBoss is not changed upstream. Patch merged upstream on master branch for 3.5.0 rebase. 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 (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 I do not think this requires doc text, as it did not affect, to the best of my knowledge, any released version. |