Created attachment 1281832 [details] engine logs Description of problem: engine-setup failed with 'Misc configuration': Command '/usr/share/ovirt-engine/dbscripts/schema.sh' failed to execute. An upgrade from 3.6.10 to latest 3.6.11.2 has failed on engine-setup [ ERROR ] Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine/dbscripts/schema.sh' failed to execute 2017-05-24 05:13:13,229 ERROR [org.ovirt.engine.core.bll.InitBackendServicesOnStartupBean] (ServerService Thread Pool -- 66) [] Failed to initialize backend: org.jboss.weld.exceptions.WeldException: WELD-000049 Un able to invoke [method] @PostConstruct private org.ovirt.engine.core.bll.pm.PmHealthCheckManager.initialize() on org.ovirt.engine.core.bll.pm.PmHealthCheckManager@5b8372e1 at org.jboss.weld.bean.AbstractClassBean.defaultPostConstruct(AbstractClassBean.java:365) [weld-core.jar:1.1.34.Final-redhat-1] at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.postConstruct(ManagedBean.java:178) [weld-core.jar:1.1.34.Final-redhat-1] aused by: org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [select * from getallfromvds(?, ?)]; nested exception is org.postgresql.util.PSQLException: The column name pretty_name was not found in this ResultSet. pretty_name column is missing, seems to caused by the fix for BZ 1446182 Version-Release number of selected component (if applicable): rhevm-3.6.11.2-0.1.el6.noarch How reproducible: Seems to be 100% on upgrade flow, from 3.6.10.2 > 3.6.11.2 Steps to Reproduce: 1. Upgrade engine from 3.6.10.2 > 3.6.11.2 Actual results: engine-setup has failed. pretty_name column is missing. Expected results: Should work Additional info: Possible related to BZ 1446182
Could you please provide logs from upgrade?
(In reply to Martin Perina from comment #1) > Could you please provide logs from upgrade? Please ignore, I'm blind :-(
I attached only engine and server logs. Attaching the engine setup log as well
Created attachment 1281887 [details] engine setup log
The issue is: 2017-05-24 04:47:45 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:941 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20170524044508-p9gw09.log', '-c', 'apply'] stderr: psql:/usr/share/ovirt-engine/dbscripts/create_views.sql:1524: ERROR: column vds_dynamic.pretty_name does not exist LINE 40: vds_dynamic.pretty_name AS pretty_name, ^ FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/create_views.sql 2017-05-24 04:47:45 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/db/schema.py", line 291, in _misc oenginecons.EngineDBEnv.PGPASS_FILE File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 946, in execute command=args[0], RuntimeError: Command '/usr/share/ovirt-engine/dbscripts/schema.sh' failed to execute 2017-05-24 04:47:45 ERROR otopi.context context._executeMethod:165 Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine/dbscripts/schema.sh' failed to execute 2017-05-24 04:47:45 DEBUG otopi.transaction transaction.abort:134 aborting 'Yum Transaction'
Upgrade from rhevm-3.6.11.1-0.1.el6.noarch (is live latest and has no pretty_name column) to rhevm-3.6.11.3-0.1.el6.noarch was successful and pretty_name column was added. verified in rhevm-3.6.11.3-0.1.el6.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1371