Bug 1328769 - [nightly 4.0] setup-engine Failed to execute stage 'Misc configuration' because of DWH scripts
Summary: [nightly 4.0] setup-engine Failed to execute stage 'Misc configuration' becau...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-dwh
Classification: oVirt
Component: Database
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.0.0-beta
: 4.0.0
Assignee: Shirly Radco
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 09:14 UTC by Kobi Hakimi
Modified: 2019-04-28 13:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-05 07:59:32 UTC
oVirt Team: Metrics
Embargoed:
rule-engine: ovirt-4.0.0+
rule-engine: blocker+
rule-engine: planning_ack+
rule-engine: devel_ack+
pnovotny: testing_ack+


Attachments (Terms of Use)
ovirt engine setup log (3.80 MB, text/plain)
2016-04-20 09:14 UTC, Kobi Hakimi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 56383 0 master MERGED history: fix bug in 3.6 views of data center statistics 2020-05-26 01:47:08 UTC

Description Kobi Hakimi 2016-04-20 09:14:40 UTC
Created attachment 1148938 [details]
ovirt engine setup log

Description of problem:
[nightly 4.0] setup-engine Failed to execute stage 'Misc configuration

Version-Release number of selected component (if applicable):
 oVirt Engine Version: 4.0.0-0.0.master.20160419161506.gitc468814.el7.centos

How reproducible:
Always

Steps to Reproduce:
Example scenario:
1. Install the ovirt-engine from nightly repository
2. Run the engine-setup with the defaults values

Actual results:
...
[ ERROR ] Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine-dwh/dbscripts/schema.sh' failed to execute
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Rolling back database schema
[ INFO  ] Clearing Engine database engine
[ INFO  ] Rolling back DWH database schema
[ INFO  ] Clearing DWH database ovirt_engine_history
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160420105445-am10vh.log
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160420110121-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed


Expected results:
finish the setup successfully.

Additional info:
see attached ovirt-engine-setup-20160420105445-am10vh.log

Comment 1 Jiri Belka 2016-04-20 13:27:57 UTC
I did not face this issue with ovirt-engine-dwh-4.0.0-0.0.master.20160420100652.git23cc138.el7.centos.noarch.

Comment 2 gregor 2016-04-26 18:37:32 UTC
today I have the same problem during update from 3.6.4 to 3.6.5 with engine-setup. After this error the database is corrupt and I can't start the engine anymore :-(

Comment 3 Yedidyah Bar David 2016-05-01 08:40:36 UTC
(In reply to gregor from comment #2)
> today I have the same problem during update from 3.6.4 to 3.6.5 with
> engine-setup. After this error the database is corrupt and I can't start the
> engine anymore :-(

Please attach:
/var/log/ovirt-engine/setup/*
/var/log/yum.log
Thanks.

Comment 4 Shirly Radco 2016-05-04 06:33:25 UTC
Hi,
Any update on this?

Comment 5 Petr Kubica 2016-06-07 11:16:36 UTC
Verified in
ovirt-engine-dwh-setup-4.0.0.1-0.0.master.20160531201540.git885483f.el7.centos.noarch
ovirt-engine-4.1.0-0.0.master.20160606111312.gitc7af584.el7.centos.noarch

also tested update from 3.6.4 to 3.6.7 (for sure)

Comment 6 Sandro Bonazzola 2016-07-05 07:59:32 UTC
oVirt 4.0.0 has been released, closing current release.

Comment 7 gregor 2017-02-27 23:18:53 UTC
(In reply to Shirly Radco from comment #4)
> Hi,
> Any update on this?

In the meantime I upgraded to latest 4.* release which "solved" the problem

Comment 8 Shirly Radco 2017-02-28 08:12:31 UTC
(In reply to gregor from comment #7)
> (In reply to Shirly Radco from comment #4)
> > Hi,
> > Any update on this?
> 
> In the meantime I upgraded to latest 4.* release which "solved" the problem

Hi,

The issue in this bug is related only to 4.0. And was discovered during qa testing before it was released.
I see that Didi asked for additional details for the issue you encountered.
But I'm glad its working now.


Note You need to log in before you can comment on or make changes to this bug.