<div dir="ltr"><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">Hi,<br><br></div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default">I'm glad that you new attempt to upgrade 3.6 to 4.0 were successfull and 4.0 is now working OK for you.<br></div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default"><br>More answers to questions inline:<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 15, 2016 at 9:50 PM, Marcin M. Jessa <span dir="ltr"><<a target="_blank" href="mailto:lists@yazzy.org">lists@yazzy.org</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">On 15/09/2016 12:58, Martin Perina wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
So something went wrong on that upgrade from 3.6 to 4.0 and it was not<br>
a good idea to do another upgrade when previous one went wrong.<br>
</blockquote>
<br>
The upgrade process went fine. The upgrade script never showed any errors.<br></blockquote><div><br><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Hmm, that's strange, because from latest setup log you sent me I'd say that 3.6 to 4.0 upgrade was not successful. But to confirm that I'd need to investigate all setup logs from 3.6 upgrade ..<br></div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
Anyway to confirm that could you please share with us also upgrade log between<br>
3.6 and 4.0? Also how did you do the upgrade (especially what OS have<br>
you used on 3.6 and if upgrade was done using engine-backup or in-place)?<br>
</blockquote>
<br>
I backed up the installation but then I ran in-place upgrade. I was told on the irc I don't need to restore from backups when I'm already on CentOS 7. Actually failing to restore from backup brought me to the IRC in the first place.<br></blockquote><div><br><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Yes, when doing in-place upgrade you don't need to do restore, that's why I asked how you performed your upgrade<br></div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
I'm on CentOS Linux release 7.2.1511 (Core)<br>
Upgrading I followed exactly the same doc you pointed to below.<br>
Except when updating to 4.1 failed, I uninstalled everything that had to do with ovirt and installed the 4.0 release.<br>
<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
More details about upgrade options from 3.6 to 4.0 can be found at:<br>
<a target="_blank" rel="noreferrer" href="http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/">http://www.ovirt.org/documenta<wbr>tion/migration-engine-3.6-to-<wbr>4.0/</a><br>
</blockquote>
Because of that doc I installed 4.1 instead of the stable 4.0 ...<br></blockquote><div><br><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Yes, that's a shame for our project to have outdated upgrade doc several month after GA release :-(<br></div><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Thanks for pointing this out, here's PR which fixes wrong repository URL:<br><br><a href="https://github.com/oVirt/ovirt-site/pull/467">https://github.com/oVirt/ovirt-site/pull/467</a><br> <br></div></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
So from current log I can see that upgrade from 3.6 to 4.0 was not<br>
successfully finished and that's why you had issues during upgrade on<br>
master.<br>
</blockquote>
Out of curiousity, where did you see that 3.6 to 4.0 update failed?<br></blockquote><div><br><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">In your setup log I can see following:<br><br> Dropping materialized views...<br> Skipping upgrade script /usr/share/ovirt-engine/dbscripts/upgrade/03_06_0000_set_version.sql, its version 03060000 is <= current version 04000860 <br> Skipping upgrade script /usr/share/ovirt-engine/dbscripts/upgrade/03_06_0010_update_haswell_vds_to_new_name.sql, its version 03060010 is <= current version 04000860</div> <br><br><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">If 3.6 was properly upgraded to 4.0, you wouldn't see any records like this, you'd see applying only 4.1 upgrade scripts, for example:<br><br> Dropping materialized views...<br> Running upgrade sql script '/usr/share/ovirt-engine/share/ovirt-engine/dbscripts/upgrade/04_01_0010_add_mac_pool_id_to_vds_group.sql'...<br> Running upgrade sql script
'/usr/share/ovirt-engine/share/ovirt-engine/dbscripts/upgrade/04_01_0020_empty_current_cd_to_null.sql'...<br><br><br></div><br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
Personaly I'd recommend you to get back into 3.6 (either by restoring<br>
from backup (if you performed in-place upgrade) or shutting down new<br>
host and starte pervious 3.6 host (if you performed upgrade using<br>
engine-backup) and do upgrade to 4.0 again. And if upgrade from 3.6 to<br>
4.0 is not successful, please share the logs again.<br>
</blockquote>
<br>
I'll try from scratch again, uninstalling everything, installing 3.6, restoring backups and upgrading to 4.0<br>
<br>
I don't want to be a party popper but to be honest you need a testing engineer. The upgrade process is way too fragile and breaks too easily...<span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
-- <br>
<br>
Marcin M. Jessa<br>
</font></span></blockquote></div><br></div></div>