Bug 1436373 - Search 'VMs: status = up' fails with exception (ERROR: column "elapsed_time" does not exist)
Summary: Search 'VMs: status = up' fails with exception (ERROR: column "elapsed_time" ...
Keywords:
Status: CLOSED DUPLICATE of bug 1416837
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Search-Backend
Version: 4.1.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Eli Mesika
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-27 19:08 UTC by Yaniv Kaul
Modified: 2017-03-28 07:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-28 07:19:50 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+


Attachments (Terms of Use)

Description Yaniv Kaul 2017-03-27 19:08:34 UTC
Description of problem:
Searching for 'Vms: status = up' fails with exception:
2017-03-27 22:04:42,984+03 ERROR [org.ovirt.engine.core.bll.SearchQuery] (default task-239) [574c2d50-3470-4e0c-9806-af30e8c87ac5] Exception: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; b
ad SQL grammar [SELECT * FROM ((SELECT distinct vms.* FROM  vms   WHERE  vms.status = '1' )  ORDER BY elapsed_time DESC NULLS LAST,vm_name ASC ) as T1 OFFSET (1 -1) LIMIT 100]; nested exception is org.postgresql
.util.PSQLException: ERROR: column "elapsed_time" does not exist
  Position: 87
        at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:99) [spring-jdbc.jar:4.2.4.RELEASE]
        at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:73) [spring-jdbc.jar:4.2.4.RELEASE]
        at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81) [spring-jdbc.jar:4.2.4.RELEASE]
        at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81) [spring-jdbc.jar:4.2.4.RELEASE]
        at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:415) [spring-jdbc.jar:4.2.4.RELEASE]
        at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:470) [spring-jdbc.jar:4.2.4.RELEASE]
        at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:480) [spring-jdbc.jar:4.2.4.RELEASE]
        at org.ovirt.engine.core.dao.VmDaoImpl.getAllUsingQuery(VmDaoImpl.java:159) [dal.jar:]
        at org.ovirt.engine.core.bll.SearchQuery.searchVmsFromDb(SearchQuery.java:227) [bll.jar:]
        at org.ovirt.engine.core.bll.SearchQuery.executeQueryCommand(SearchQuery.java:152) [bll.jar:]
        at org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:110) [bll.jar:]
        at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:]
        at org.ovirt.engine.core.bll.executor.DefaultBackendQueryExecutor.execute(DefaultBackendQueryExecutor.java:14) [bll.jar:]
        at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:579) [bll.jar:]
        at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:547) [bll.jar:]
        at sun.reflect.GeneratedMethodAccessor122.invoke(Unknown Source) [:1.8.0_121]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121]


...

Caused by: org.postgresql.util.PSQLException: ERROR: column "elapsed_time" does not exist
  Position: 87
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)


Version-Release number of selected component (if applicable):
4.1.0.4-0.1.el7

Comment 1 Red Hat Bugzilla Rules Engine 2017-03-27 19:08:39 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Allon Mureinik 2017-03-28 07:19:50 UTC
This was already reported in bug 1416837 and fixed in 4.1.1.

*** This bug has been marked as a duplicate of bug 1416837 ***


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