Hide Forgot
Created attachment 555941 [details] engine-cleanup Description of problem: shutting down ovirt-engine should stop ETL, if running, and starting it up again, if it ran before the shutdown, when it starts. Version-Release number of selected component (if applicable): F-16 -> ovirt-engine-3.0.0_0001-7, ovirt-reports (git 3.0) How reproducible: Always Steps to Reproduce: 1.Install ovirt-engine & run engine-setup 2.Install ovirt-dwh & ovirt-report 3.start ovirt-etl 3.Uninstall ovirt-engine Actual results: Uninstall fails to remove the Database (engine) Expected results: should stop ETL Additional info: should stop ETL, if running,while uninstalling and starting it up again during installation, if it ran before the shutdown, when it starts.
I'm missing multiple versions here: Which version of oVirt-Engine did you use? the latest is based on JBoss AS7, and I don't think the ovirt-dwh/reports supports that. more than that- I don't know ovirt-engine-3.0.0_0001-7, where did you take it from? Also, which version of ovirt-dwh did you used?
ovirt-engine version prior to today's version with the AS7 (ovirt-engine-3.0.0_0001-7),the first rpm version. I use reports & dwh from GIT. In general the ovirt-engine should stop ETL in order to dropdb, otherwise it will fail ovirt-engine uninstall
(In reply to comment #2) > ovirt-engine version prior to today's version with the AS7 > (ovirt-engine-3.0.0_0001-7),the first rpm version. I don't know such a release....
Can
David Please provide repository locations or SHA from upstream git repositories with versions that you have used for this check. Thanks.
ovirt-engine version prior to the first version with the AS7 (ovirt-engine-3.0.0_0001-7). I use reports & dwh from GIT. F-16 -> ovirt-engine-3.0.0_0001-7, ovirt-reports (git 3.0) Cant you use the latest versions, see if it happens there ? if not, fixed already
All connections are cleared during the cleanup operation on the local machine. Besides, the 3.0 is no longer developed. If the problem still exists in the newer version (3.2 is the current beta release), please open the bug with the new data.