[ovirt-users] Re: Ovirt 4.2.4 upgrade

2018-05-27 Thread Maton, Brett
I rebuilt that environment, I'll try to recreate the scenario and provide the information requested. On 27 May 2018 at 09:17, Eli Mesika wrote: > Hi > > The provider_binding_host_id is a new table added recently , can you > please attach the output of the following query on your database : > > s

[ovirt-users] Re: Ovirt 4.2.4 upgrade

2018-05-27 Thread Eli Mesika
Hi The provider_binding_host_id is a new table added recently , can you please attach the output of the following query on your database : select * from schema_version order by id desc; Thanks On Fri, May 25, 2018 at 2:30 PM, Maton, Brett wrote: > It would be from the last 4.2.3 release in th

[ovirt-users] Re: Ovirt 4.2.4 upgrade

2018-05-25 Thread Martin Perina
On Fri, May 25, 2018 at 1:30 PM, Maton, Brett wrote: > It would be from the last 4.2.3 release in the ovirt-4.2-pre repositories > > I haven't got the logs unfortunately, I'll try to recreate the scenario > over the weekend. > ​Please try and share upgrade logs. I've just quickly tried the upgra

[ovirt-users] Re: Ovirt 4.2.4 upgrade

2018-05-25 Thread Maton, Brett
It would be from the last 4.2.3 release in the ovirt-4.2-pre repositories I haven't got the logs unfortunately, I'll try to recreate the scenario over the weekend. On 25 May 2018 at 12:09, Martin Perina wrote: > Hi, > > from which oVirt version are you upgrading to 4.2.4? Could you please > sha

[ovirt-users] Re: Ovirt 4.2.4 upgrade

2018-05-25 Thread Martin Perina
Hi, from which oVirt version are you upgrading to 4.2.4? Could you please share with us complete upgrade logs from engine host? Thanks Martin On Fri, May 25, 2018 at 10:38 AM, Sandro Bonazzola wrote: > > > 2018-05-25 9:41 GMT+02:00 Maton, Brett : > >> The 4.2.4 upgrade appears to have a data

[ovirt-users] Re: Ovirt 4.2.4 upgrade

2018-05-25 Thread Sandro Bonazzola
2018-05-25 9:41 GMT+02:00 Maton, Brett : > The 4.2.4 upgrade appears to have a database issue, i'm seeing these > errors in the postgresql logs: > > 2018-05-24 16:27:08.292 UTC ERROR: relation "provider_binding_host_id" > does not exist at character 15 > 2018-05-24 16:27:08.292 UTC QUERY: SELECT