Well, this is the only explanation I was able to think of as I haven't been able to reproduce it locally and definitely there was not any change in 3.5 upgrade scripts for several months (the 03_05_0580_add_default_instance_types.sql script was changed last time on Jun 2nd 2014). Anyway it happen again, we can investigate it more. Thanks Martin On Tue, Jun 7, 2016 at 8:37 AM, Barak Korren <bkorren@redhat.com> wrote:
On 6 June 2016 at 11:46, Martin Perina <mperina@redhat.com> wrote:
No it's not, this is some strange failure in 3.5 upgrade script which seems to me impossible. The patch [1] didn't contain any db related stuff, so upgrade from master before this patch to master with this patch shouldn't fail (and I just verified locally that this upgrade works fine). So I assume this was some kind of mess in db content prior the upgrade job.
This is close to impossible, the upgrade job removes the postgresql package and deletes "/var/lib/pgsql/data" as can be seen here:
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/ovirt-engine_upg...