[ovirt-users] after upgrade from 4.0.4 to 4.1.1, no more gettagsbyparent_id

[Yedidyah Bar David]

On Tue, Apr 25, 2017 at 12:14 PM, Fabrice Bacchella
<fabrice.bacchella at orange.fr> wrote:
>
>> Le 25 avr. 2017 à 10:27, Yedidyah Bar David <didi at redhat.com> a écrit :
>>
>>
>
>> So all was good until you changed (downgraded?) your pg client? So
>> perhaps try to revert that. Although if you didn't change your jdbc
>> library, I do not think this should have affected you. But in any
>> case, if the failure was not caused by running 'engine-setup', it's
>> most likely not due to a bug in engine-setup, but elsewhere.
>
> Possible, but for the moment, I need a way to get out of this trap. My ovirt engine is broken.

Your db dump does have gettagsbyparent_id, so that's not the problem.
I am not an expert in the engine side, no idea otherwise.

My guess is that it might be related to:

2017-04-24 16:52:23,700+02 WARN
[org.springframework.jdbc.core.metadata.CallMetaDataProvider]
(ServerService Thread Pool -- 49) Error while retrieving metadata for
procedure columns: org.postgresql.util.PSQLException: Cannot cast type
String to boolean: "2"
2017-04-24 16:52:23,727+02 WARN
[org.springframework.jdbc.core.metadata.CallMetaDataProvider]
(ServerService Thread Pool -- 53) Error while retrieving metadata for
procedure columns: org.postgresql.util.PSQLException: Cannot cast type
String to boolean: "2"
2017-04-24 16:52:23,759+02 WARN
[org.springframework.jdbc.core.metadata.CallMetaDataProvider]
(ServerService Thread Pool -- 49) Error while retrieving metadata for
procedure columns: org.postgresql.util.PSQLException: Cannot cast type
String to boolean: "2"

Perhaps try to start the engine with DEBUG level info to get more info.
Edit /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.xml.in
and replace each 'INFO' with 'DEBUG', then restart the engine. Adding
Eli.

Best,
-- 
Didi