<div dir="ltr">The engine version I am attempting to upgrade from was built from:<br>---------------<br>commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679<br>tree: ee9ee41c3e855c26f491c77fda9622c05af3fc54<br>parent: 82644cae97f3c546ee631ae79c925c91e7bed836<br>
<br>userportal,webadmin: Change remove message<br>Change-Id: Ia934e33d1a975e0235e1a1ffae0c8a4a7af66f10<br>Signed-off-by: Alexander Wels <<a href="mailto:awels@redhat.com">awels@redhat.com</a>><br>---------------<br>
<div class="gmail_extra">Thus it is version 3.3 and not 3.2. The upgrade (built from this master this AM) was attempted ovirt a fresh install of the packages built from the above commit. I also confirmed the install was fully functional.<br>
<br></div><div class="gmail_extra">- DHC<br></div><div class="gmail_extra"><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 29, 2013 at 4:08 PM, Doron Fediuck <span dir="ltr"><<a href="mailto:dfediuck@redhat.com" target="_blank">dfediuck@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im"><br>
<br>
----- Original Message -----<br>
| From: "Alon Bar-Lev" <<a href="mailto:alonbl@redhat.com">alonbl@redhat.com</a>><br>
| To: "Doron Fediuck" <<a href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>><br>
| Cc: "Dead Horse" <<a href="mailto:deadhorseconsulting@gmail.com">deadhorseconsulting@gmail.com</a>>, "users" <<a href="mailto:users@ovirt.org">users@ovirt.org</a>>, "Dave Chen" <<a href="mailto:wei.d.chen@intel.com">wei.d.chen@intel.com</a>>, "Eli<br>
| Mesika" <<a href="mailto:emesika@redhat.com">emesika@redhat.com</a>><br>
</div><div><div class="h5">| Sent: Monday, July 29, 2013 11:51:35 PM<br>
| Subject: Re: [Users] upgrade to latest master not working<br>
|<br>
|<br>
|<br>
| ----- Original Message -----<br>
| > From: "Doron Fediuck" <<a href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>><br>
| > To: "Alon Bar-Lev" <<a href="mailto:alonbl@redhat.com">alonbl@redhat.com</a>><br>
| > Cc: "Dead Horse" <<a href="mailto:deadhorseconsulting@gmail.com">deadhorseconsulting@gmail.com</a>>, "users"<br>
| > <<a href="mailto:users@ovirt.org">users@ovirt.org</a>>, "Dave Chen" <<a href="mailto:wei.d.chen@intel.com">wei.d.chen@intel.com</a>>, "Eli<br>
| > Mesika" <<a href="mailto:emesika@redhat.com">emesika@redhat.com</a>><br>
| > Sent: Monday, July 29, 2013 11:43:46 PM<br>
| > Subject: Re: [Users] upgrade to latest master not working<br>
| ><br>
| ><br>
| ><br>
| > ----- Original Message -----<br>
| > | From: "Alon Bar-Lev" <<a href="mailto:alonbl@redhat.com">alonbl@redhat.com</a>><br>
| > | To: "Doron Fediuck" <<a href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>><br>
| > | Cc: "Dead Horse" <<a href="mailto:deadhorseconsulting@gmail.com">deadhorseconsulting@gmail.com</a>>, "users"<br>
| > | <<a href="mailto:users@ovirt.org">users@ovirt.org</a>>, "Dave Chen" <<a href="mailto:wei.d.chen@intel.com">wei.d.chen@intel.com</a>>, "Eli<br>
| > | Mesika" <<a href="mailto:emesika@redhat.com">emesika@redhat.com</a>><br>
| > | Sent: Monday, July 29, 2013 11:31:42 PM<br>
| > | Subject: Re: [Users] upgrade to latest master not working<br>
| > |<br>
| > |<br>
| > |<br>
| > | ----- Original Message -----<br>
| > | > From: "Doron Fediuck" <<a href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>><br>
| > | > To: "Alon Bar-Lev" <<a href="mailto:alonbl@redhat.com">alonbl@redhat.com</a>><br>
| > | > Cc: "Dead Horse" <<a href="mailto:deadhorseconsulting@gmail.com">deadhorseconsulting@gmail.com</a>>, "users"<br>
| > | > <<a href="mailto:users@ovirt.org">users@ovirt.org</a>>, "Dave Chen" <<a href="mailto:wei.d.chen@intel.com">wei.d.chen@intel.com</a>>, "Eli<br>
| > | > Mesika" <<a href="mailto:emesika@redhat.com">emesika@redhat.com</a>><br>
| > | > Sent: Monday, July 29, 2013 11:27:41 PM<br>
| > | > Subject: Re: [Users] upgrade to latest master not working<br>
| > | ><br>
| > | ><br>
| > | ><br>
| > | > ----- Original Message -----<br>
| > | > | From: "Alon Bar-Lev" <<a href="mailto:alonbl@redhat.com">alonbl@redhat.com</a>><br>
| > | > | To: "Dead Horse" <<a href="mailto:deadhorseconsulting@gmail.com">deadhorseconsulting@gmail.com</a>><br>
| > | > | Cc: "users" <<a href="mailto:users@ovirt.org">users@ovirt.org</a>>, "Doron Fediuck" <<a href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>>,<br>
| > | > | "Dave<br>
| > | > | Chen" <<a href="mailto:wei.d.chen@intel.com">wei.d.chen@intel.com</a>>, "Eli<br>
| > | > | Mesika" <<a href="mailto:emesika@redhat.com">emesika@redhat.com</a>><br>
| > | > | Sent: Monday, July 29, 2013 10:47:01 PM<br>
| > | > | Subject: Re: [Users] upgrade to latest master not working<br>
| > | > |<br>
| > | > |<br>
| > | > |<br>
| > | > | ----- Original Message -----<br>
| > | > | > From: "Dead Horse" <<a href="mailto:deadhorseconsulting@gmail.com">deadhorseconsulting@gmail.com</a>><br>
| > | > | > To: "Alon Bar-Lev" <<a href="mailto:alonbl@redhat.com">alonbl@redhat.com</a>><br>
| > | > | > Cc: "users" <<a href="mailto:users@ovirt.org">users@ovirt.org</a>><br>
| > | > | > Sent: Monday, July 29, 2013 10:41:34 PM<br>
| > | > | > Subject: Re: [Users] upgrade to latest master not working<br>
| > | > | ><br>
| > | > | > server.log attached<br>
| > | > |<br>
| > | > | Thanks!<br>
| > | > |<br>
| > | > | My guess is that I8ce3448a[1] broke master.<br>
| > | > |<br>
| > | > | [1] <a href="http://gerrit.ovirt.org/#/c/14605/" target="_blank">http://gerrit.ovirt.org/#/c/14605/</a><br>
| > | > |<br>
| > | ><br>
| > | > Works perfectly on my Gentoo with master.<br>
| > | ><br>
| > |<br>
| > | I doubt you are upgrading from 3.2 :)<br>
| > |<br>
| ><br>
| > Just did:<br>
| ><br>
| > $ git checkout origin/engine_3.2<br>
| > $ cd backend/manager/dbscripts/<br>
| > $ ./create_db.sh -d upgrade32-test -u engine<br>
| > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts<br>
| > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts<br>
| > Creating the database: upgrade32-test<br>
| > dropdb: database removal failed: ERROR: database "upgrade32-test" does not<br>
| > exist<br>
| > user name is: engine<br>
| > Creating tables...<br>
| > Creating functions...<br>
| > Creating common functions...<br>
| > Inserting data ...<br>
| > Inserting pre-defined roles ...<br>
| > Running upgrade scripts...<br>
| > upgrade script detected a change in Config, View or Stored Procedure...<br>
| > Running upgrade sql script upgrade/pre_upgrade/0000_config.sql ...<br>
| ><br>
| > ...<br>
| ><br>
| > Creating stored procedures from vm_templates_sp.sql ...<br>
| > Running upgrade sql script<br>
| > upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ...<br>
| > Running upgrade sql script<br>
| > upgrade/post_upgrade/0020_create_materialized_views.sql ...<br>
| > Refreshing materialized views...<br>
| > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts<br>
| ><br>
| > $ git checkout master<br>
| > $ cd ../../../packaging/dbscripts/<br>
| > $ ./upgrade.sh -d upgrade32-test -u engine<br>
| > upgrade script detected a change in Config, View or Stored Procedure...<br>
| > Running upgrade sql script upgrade/pre_upgrade/0000_config.sql ...<br>
| ><br>
| > ...<br>
| ><br>
| > Creating stored procedures from vms_sp.sql ...<br>
| > Running upgrade sql script<br>
| > upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ...<br>
| > Running upgrade sql script<br>
| > upgrade/post_upgrade/0020_create_materialized_views.sql ...<br>
| > Refreshing materialized views...<br>
| > Done.<br>
| > <br>
| ><br>
| > Seems to work well. Am I missing something?<br>
| ><br>
|<br>
| Start jboss?<br>
|<br>
| Please take over this issue, you have relevant logs, and a cooperative user.<br>
|<br>
| Thanks,<br>
| Alon<br>
|<br>
<br>
</div></div>Since jboss is up and running very well after upgrade I do not see a problem.<br>
Is it possible that the install / upgrade process didn't complete due to other<br>
errors ending up with this state?<br>
<br>
In the meantime you can manually create the missing function to get your<br>
setup running. The only problem is that if my assumption is correct on<br>
upgrade not finishing, you will hit the next db change as an error. So<br>
I'd try and look at the install/upgrade log files to see if db upgrade<br>
failed at some point.<br>
</blockquote></div><br></div></div>