Bug 1284438
Summary: | engine-setup fails complaining that DWH is running but it's not running | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Julio Entrena Perez <jentrena> |
Component: | ovirt-engine-setup | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | bazulay, ecohen, gklein, jentrena, lsurette, rbalakri, Rhev-m-bugs, sradco, yeylon, ylavi |
Target Milestone: | ovirt-3.6.1 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | integration | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-01 06:33:48 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: | 1283458 |
Description
Julio Entrena Perez
2015-11-23 10:43:07 UTC
In the setup log file: 2015-11-23 10:50:41 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:936 execute-output: ('/sbin/service', 'ovirt-engine-dwhd', 'status') stdout: ovirt-engine-dwhd is stopped But later: 2015-11-23 10:50:42 DEBUG otopi.context context._executeMethod:142 Stage transaction-prepare METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.core.single_etl.Plugin._transactionBegin 2015-11-23 10:50:42 DEBUG otopi.ovirt_engine_setup.engine_common.database database.execute:171 Database: 'None', Statement: ' select * from GetDwhHistoryTimekeepingByVarName( %(name)s ) ', args: {'name': 'DwhCurrentlyRunning'} 2015-11-23 10:50:42 DEBUG otopi.ovirt_engine_setup.engine_common.database database.execute:176 Creating own connection 2015-11-23 10:50:42 DEBUG otopi.ovirt_engine_setup.engine_common.database database.execute:221 Result: [{'var_value': '1', 'var_datetime': None, 'var_name': 'DwhCurrentlyRunning'}] 2015-11-23 10:50:42 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.core.single_etl single_etl._transactionBegin:136 dwhd is currently running. Its hostname is rhevm3-375.usersys.**FILTERED**.com. Please stop it before running Setup. 2015-11-23 10:50:42 DEBUG otopi.context context._executeMethod:156 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 146, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-dwh/core/single_etl.py", line 139, in _transactionBegin raise RuntimeError(_('dwhd is currently running')) RuntimeError: dwhd is currently running Seems a timing issue: starting engine, starting dwh, stopping dwh and giving it a minute before re-running the installer seems to allow the installer to proceed. When the installer is run for the first time dwh is running and the installer stops it, but it seems that there is not enough time for the 'DwhCurrentlyRunning' database value to be updated. Shouldn't checking that the service is stopped by enough? (In reply to Julio Entrena Perez from comment #3) > Seems a timing issue: starting engine, starting dwh, stopping dwh and giving > it a minute before re-running the installer seems to allow the installer to > proceed. > > When the installer is run for the first time dwh is running and the > installer stops it, but it seems that there is not enough time for the > 'DwhCurrentlyRunning' database value to be updated. > > Shouldn't checking that the service is stopped by enough? IMO Yes. Shirly? Can we make sure that dwhd exits, that is - 'service ovirt-engine-dwhd stop' returns - only when all of its threads finished? We have a similar bug 1075013 about the engine, probably didn't cause enough trouble yet. BTW, I am pretty certain this affects 3.5 too, also not sure it's a 3.6/beta blocker. All threads and connections are closed when dwh exists. Now got this error on a different flow and filed bug 1286441. Following a private discussion, closing as duplicate of bug 1286441. Please reopen if relevant. Thanks. *** This bug has been marked as a duplicate of bug 1286441 *** |