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
Steps to Reproduce:
1. Install the ovirt-engine from nightly repository
2. Run the engine-setup with the defaults values
[ 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
finish the setup successfully.
see attached ovirt-engine-setup-20160420105445-am10vh.log
I did not face this issue with ovirt-engine-dwh-4.0.0-0.0.master.20160420100652.git23cc138.el7.centos.noarch.
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 :-(
(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 :-(
Any update on this?
also tested update from 3.6.4 to 3.6.7 (for sure)
oVirt 4.0.0 has been released, closing current release.
(In reply to Shirly Radco from comment #4)
> Any update on this?
In the meantime I upgraded to latest 4.* release which "solved" the problem
(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
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.