Re: [Users] upgrade to latest master not working
Big thanks to all. I can have a deep breath eventually when I know it's not this patch set ( http://gerrit.ovirt.org/#/c/14605/) broke the master, we are glad to do something if there is any potential issue relevant with the patch sets we submitted. Best Regards, Dave Chen > -Original Message- > From: Doron Fediuck [mailto:dfedi...@redhat.com] > Sent: Wednesday, July 31, 2013 4:28 AM > To: Dead Horse > Cc: Alon Bar-Lev; users; Chen, Wei D; Eli Mesika > Subject: Re: [Users] upgrade to latest master not working > > Big thanks DHC for your time and efforts. > > Since neither of us managed to reproduce the issue I suggest we drop it for > now. If someone else will hit into it, we should try and > get more > info on a possible failure which will not complete the db upgrade. > > Thanks again, > Doron > > - Original Message - > | From: "Dead Horse" > | To: "Doron Fediuck" > | Cc: "Alon Bar-Lev" , "users" , "Dave > Chen" , "Eli Mesika" > | > | Sent: Tuesday, July 30, 2013 11:20:01 PM > | Subject: Re: [Users] upgrade to latest master not working > | > | Ok, so something from yesterday morning to today changed. I again > | rebuilt engine from the latest commit this AM. Accordingly I also > | built this mornings latest commits of otopi and ovirt-host-deploy. I > | then attempted upgrade and this time I did not note any major issues. > | The upgrade appears to have succeeded, and engine starts and runs. > | The only things that caused failures during upgrade were: > | - If the previous version ovirt-engine-sdk is not removed manually and > | replaced with ovirt-engine-sdk-python engine-upgrade fails due to > | package dependency issues. (which then upsets ovirt-iso-uploader, > | ovirt-image-uploader, ovirt-log-collector dependencies on > | ovirt-engine-sdk) > | - If there is a leftover releasepreview directory engine-upgrade will > | not run > | > | There were some error messages in the engine log griping about "Could > | not parse option AutoRecoveryAllowedTypes value". I have attached the > | engine log file from the first start of the engine after upgrade. > | > | The other minor thing to note is that the default ovirt.brand theme is > | not working. The CSS styles are not being applied. Changes to > | welcome_page.template and messages.properties were picked up however. > | > | - DHC > | > | > | > | On Tue, Jul 30, 2013 at 11:04 AM, Doron Fediuck wrote: > | > | > > | > > | > - Original Message ----- > | > | From: "Dead Horse" > | > | To: "Doron Fediuck" > | > | Cc: "Alon Bar-Lev" , "users" , > | > "Dave Chen" , "Eli Mesika" > | > | > | > | Sent: Tuesday, July 30, 2013 6:55:18 PM > | > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | The only error I can find in the upgrade log is: > | > | 2013-07-29 14:06:28 DEBUG > | > | otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch > | > | 0:3.3.0-20.fc18 - u > | > | 2013-07-29 14:06:28 INFO otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.info:88 Yum update: 10/18: ovirt-engine > | > | 2013-07-29 14:06:35 DEBUG > | > | otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch > | > | 0:3.3.0-20.fc18 - u > | > | 2013-07-29 14:06:35 DEBUG > | > | otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine-3.3.0-20.fc18.noarch > | > | 2013-07-29 14:06:37 INFO otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.info:88 Yum update: 11/18: ovirt-engine-dbscripts > | > | 2013-07-29 14:06:38 DEBUG > | > | otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: > | > ovirt-engine-dbscripts-3.3.0-20.fc18.noarch > | > | 2013-07-29 14:06:38 DEBUG > | > | otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine-backend Traceback > | > | (most recent call last): > | > | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line > | > | 464, in callback > | > | self._unInstStop( bytes, total, h ) > | > | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line > | > | 564, in _unInstStop > | > | self.total_actions) > | > | File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line > | > | 204, in event > | > | package=package.name, > | > | AttributeError: 'str' object has no attrib
Re: [Users] upgrade to latest master not working
Agreed, I did revert my victim VM back the pre-upgrade snapshot and retry the upgrade with the same results with yesterdays packages.I had watch on the logs but I did not see any DB upgrade failures. Given that I figured for the heck of it I would just rebuild with this mornings latest commits to see if the issue still persisted, I actually fully expected it to fail the same. However to my surprise it did not fail, thus I assume something changed between yesterday morning this morning that allowed things to work. for grins the packages I used yesterday were generated from: engine commit: ec2b57124edd5ae1fa41e986adadfefb9c5f1aa7 otopi commit: 8e3e3c27cbcd4330143d571a3ce8caa36c6d20ef ovirt-host-deply commit: 35a5b5f5e6d6c240ef1d20904bc06498b0ed81e1 and the packages I generated this morning that worked were from: engine commit: 28251d9acd1ecbe39b9b79e7e2e69342f57c9bd7 otopi commit: 10892fbf3fe805cea416dfa3ba628f98ffa88b3e ovirt-host-deply commit: e9c98c67dcdfca21091141bcb732727f50eb97d1 - DHC On Tue, Jul 30, 2013 at 3:27 PM, Doron Fediuck wrote: > Big thanks DHC for your time and efforts. > > Since neither of us managed to reproduce the issue > I suggest we drop it for now. If someone else will hit > into it, we should try and get more info on a possible > failure which will not complete the db upgrade. > > Thanks again, > Doron > > - Original Message - > | From: "Dead Horse" > | To: "Doron Fediuck" > | Cc: "Alon Bar-Lev" , "users" , > "Dave Chen" , "Eli Mesika" > | > | Sent: Tuesday, July 30, 2013 11:20:01 PM > | Subject: Re: [Users] upgrade to latest master not working > | > | Ok, so something from yesterday morning to today changed. I again rebuilt > | engine from the latest commit this AM. Accordingly I also built this > | mornings latest commits of otopi and ovirt-host-deploy. I then attempted > | upgrade and this time I did not note any major issues. The upgrade > appears > | to have succeeded, and engine starts and runs. > | The only things that caused failures during upgrade were: > | - If the previous version ovirt-engine-sdk is not removed manually and > | replaced with ovirt-engine-sdk-python engine-upgrade fails due to package > | dependency issues. (which then upsets ovirt-iso-uploader, > | ovirt-image-uploader, ovirt-log-collector dependencies on > ovirt-engine-sdk) > | - If there is a leftover releasepreview directory engine-upgrade will not > | run > | > | There were some error messages in the engine log griping about "Could not > | parse option AutoRecoveryAllowedTypes value". I have attached the engine > | log file from the first start of the engine after upgrade. > | > | The other minor thing to note is that the default ovirt.brand theme is > not > | working. The CSS styles are not being applied. Changes to > | welcome_page.template and messages.properties were picked up however. > | > | - DHC > | > | > | > | On Tue, Jul 30, 2013 at 11:04 AM, Doron Fediuck > wrote: > | > | > > | > > | > - Original Message - > | > | From: "Dead Horse" > | > | To: "Doron Fediuck" > | > | Cc: "Alon Bar-Lev" , "users" , > | > "Dave Chen" , "Eli Mesika" > | > | > | > | Sent: Tuesday, July 30, 2013 6:55:18 PM > | > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | The only error I can find in the upgrade log is: > | > | 2013-07-29 14:06:28 DEBUG otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 > - u > | > | 2013-07-29 14:06:28 INFO otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.info:88 Yum update: 10/18: ovirt-engine > | > | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 > - u > | > | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine-3.3.0-20.fc18.noarch > | > | 2013-07-29 14:06:37 INFO otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.info:88 Yum update: 11/18: ovirt-engine-dbscripts > | > | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: > | > ovirt-engine-dbscripts-3.3.0-20.fc18.noarch > | > | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager > | > | yumpackager.verbose:84 Yum Done: ovirt-engine-backend > | > | Traceback (most recent call last): > | > | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 464, > in > | > | callba
Re: [Users] upgrade to latest master not working
Big thanks DHC for your time and efforts. Since neither of us managed to reproduce the issue I suggest we drop it for now. If someone else will hit into it, we should try and get more info on a possible failure which will not complete the db upgrade. Thanks again, Doron - Original Message - | From: "Dead Horse" | To: "Doron Fediuck" | Cc: "Alon Bar-Lev" , "users" , "Dave Chen" , "Eli Mesika" | | Sent: Tuesday, July 30, 2013 11:20:01 PM | Subject: Re: [Users] upgrade to latest master not working | | Ok, so something from yesterday morning to today changed. I again rebuilt | engine from the latest commit this AM. Accordingly I also built this | mornings latest commits of otopi and ovirt-host-deploy. I then attempted | upgrade and this time I did not note any major issues. The upgrade appears | to have succeeded, and engine starts and runs. | The only things that caused failures during upgrade were: | - If the previous version ovirt-engine-sdk is not removed manually and | replaced with ovirt-engine-sdk-python engine-upgrade fails due to package | dependency issues. (which then upsets ovirt-iso-uploader, | ovirt-image-uploader, ovirt-log-collector dependencies on ovirt-engine-sdk) | - If there is a leftover releasepreview directory engine-upgrade will not | run | | There were some error messages in the engine log griping about "Could not | parse option AutoRecoveryAllowedTypes value". I have attached the engine | log file from the first start of the engine after upgrade. | | The other minor thing to note is that the default ovirt.brand theme is not | working. The CSS styles are not being applied. Changes to | welcome_page.template and messages.properties were picked up however. | | - DHC | | | | On Tue, Jul 30, 2013 at 11:04 AM, Doron Fediuck wrote: | | > | > | > - Original Message - | > | From: "Dead Horse" | > | To: "Doron Fediuck" | > | Cc: "Alon Bar-Lev" , "users" , | > "Dave Chen" , "Eli Mesika" | > | | > | Sent: Tuesday, July 30, 2013 6:55:18 PM | > | Subject: Re: [Users] upgrade to latest master not working | > | | > | The only error I can find in the upgrade log is: | > | 2013-07-29 14:06:28 DEBUG otopi.plugins.otopi.packagers.yumpackager | > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u | > | 2013-07-29 14:06:28 INFO otopi.plugins.otopi.packagers.yumpackager | > | yumpackager.info:88 Yum update: 10/18: ovirt-engine | > | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager | > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u | > | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager | > | yumpackager.verbose:84 Yum Done: ovirt-engine-3.3.0-20.fc18.noarch | > | 2013-07-29 14:06:37 INFO otopi.plugins.otopi.packagers.yumpackager | > | yumpackager.info:88 Yum update: 11/18: ovirt-engine-dbscripts | > | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager | > | yumpackager.verbose:84 Yum Done: | > ovirt-engine-dbscripts-3.3.0-20.fc18.noarch | > | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager | > | yumpackager.verbose:84 Yum Done: ovirt-engine-backend | > | Traceback (most recent call last): | > | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 464, in | > | callback | > | self._unInstStop( bytes, total, h ) | > | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 564, in | > | _unInstStop | > | self.total_actions) | > | File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 204, in | > | event | > | package=package.name, | > | AttributeError: 'str' object has no attribute 'name' | > | FATAL ERROR: python callback | > failed, aborting! | > | | > | To test the database upgrade I will revert to a previous snapshot of the | > | debug VM, capture the dbase from the previous engine version, re-run | > | upgrade, dump the upgraded database, restore the previous, and then test | > a | > | manual run of the database upgrade script. | > | | > | Does this sound prudent? | > | - DHC | > | | > | > Yes. Although lots of work, it may show if there's a DB upgrade bug we | > missed, or indeed the general upgrade procedure has / had an issue. | > | > | | > | On Tue, Jul 30, 2013 at 5:54 AM, Doron Fediuck | > wrote: | > | | > | > Thanks. | > | > So this leads me further to the upgrade procedure | > | > which may have fail, thus not completing the DB upgrade. | > | > Can you please check the upgrade logs to see if something | > | > matches this flow? | > | > | > | > - Original Message
Re: [Users] upgrade to latest master not working
- Original Message - > From: "Dead Horse" > To: "Doron Fediuck" > Cc: "Alon Bar-Lev" , "users" , "Dave > Chen" , "Eli Mesika" > > Sent: Tuesday, July 30, 2013 11:20:01 PM > Subject: Re: [Users] upgrade to latest master not working > > Ok, so something from yesterday morning to today changed. I again rebuilt > engine from the latest commit this AM. Accordingly I also built this > mornings latest commits of otopi and ovirt-host-deploy. I then attempted > upgrade and this time I did not note any major issues. The upgrade appears > to have succeeded, and engine starts and runs. > The only things that caused failures during upgrade were: > - If the previous version ovirt-engine-sdk is not removed manually and > replaced with ovirt-engine-sdk-python engine-upgrade fails due to package > dependency issues. (which then upsets ovirt-iso-uploader, > ovirt-image-uploader, ovirt-log-collector dependencies on ovirt-engine-sdk) > - If there is a leftover releasepreview directory engine-upgrade will not > run > > There were some error messages in the engine log griping about "Could not > parse option AutoRecoveryAllowedTypes value". I have attached the engine > log file from the first start of the engine after upgrade. > > The other minor thing to note is that the default ovirt.brand theme is not > working. The CSS styles are not being applied. Changes to > welcome_page.template and messages.properties were picked up however. > Yes, this is known issue, the patch was reverted because of some issues, now ready[1] [1] http://gerrit.ovirt.org/#/c/17484/ > - DHC > > > > On Tue, Jul 30, 2013 at 11:04 AM, Doron Fediuck wrote: > > > > > > > - Original Message - > > | From: "Dead Horse" > > | To: "Doron Fediuck" > > | Cc: "Alon Bar-Lev" , "users" , > > "Dave Chen" , "Eli Mesika" > > | > > | Sent: Tuesday, July 30, 2013 6:55:18 PM > > | Subject: Re: [Users] upgrade to latest master not working > > | > > | The only error I can find in the upgrade log is: > > | 2013-07-29 14:06:28 DEBUG otopi.plugins.otopi.packagers.yumpackager > > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u > > | 2013-07-29 14:06:28 INFO otopi.plugins.otopi.packagers.yumpackager > > | yumpackager.info:88 Yum update: 10/18: ovirt-engine > > | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager > > | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u > > | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager > > | yumpackager.verbose:84 Yum Done: ovirt-engine-3.3.0-20.fc18.noarch > > | 2013-07-29 14:06:37 INFO otopi.plugins.otopi.packagers.yumpackager > > | yumpackager.info:88 Yum update: 11/18: ovirt-engine-dbscripts > > | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager > > | yumpackager.verbose:84 Yum Done: > > ovirt-engine-dbscripts-3.3.0-20.fc18.noarch > > | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager > > | yumpackager.verbose:84 Yum Done: ovirt-engine-backend > > | Traceback (most recent call last): > > | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 464, in > > | callback > > | self._unInstStop( bytes, total, h ) > > | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 564, in > > | _unInstStop > > | self.total_actions) > > | File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 204, in > > | event > > | package=package.name, > > | AttributeError: 'str' object has no attribute 'name' > > | FATAL ERROR: python callback > | > failed, aborting! > > | > > | To test the database upgrade I will revert to a previous snapshot of the > > | debug VM, capture the dbase from the previous engine version, re-run > > | upgrade, dump the upgraded database, restore the previous, and then test > > a > > | manual run of the database upgrade script. > > | > > | Does this sound prudent? > > | - DHC > > | > > > > Yes. Although lots of work, it may show if there's a DB upgrade bug we > > missed, or indeed the general upgrade procedure has / had an issue. > > > > | > > | On Tue, Jul 30, 2013 at 5:54 AM, Doron Fediuck > > wrote: > > | > > | > Thanks. > > | > So this leads me further to the upgrade procedure > > | > which may have fail, thus not completing the DB upgrade. > > | > Can you p
Re: [Users] upgrade to latest master not working
- Original Message - | From: "Dead Horse" | To: "Doron Fediuck" | Cc: "Alon Bar-Lev" , "users" , "Dave Chen" , "Eli Mesika" | | Sent: Tuesday, July 30, 2013 6:55:18 PM | Subject: Re: [Users] upgrade to latest master not working | | The only error I can find in the upgrade log is: | 2013-07-29 14:06:28 DEBUG otopi.plugins.otopi.packagers.yumpackager | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u | 2013-07-29 14:06:28 INFO otopi.plugins.otopi.packagers.yumpackager | yumpackager.info:88 Yum update: 10/18: ovirt-engine | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager | yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u | 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager | yumpackager.verbose:84 Yum Done: ovirt-engine-3.3.0-20.fc18.noarch | 2013-07-29 14:06:37 INFO otopi.plugins.otopi.packagers.yumpackager | yumpackager.info:88 Yum update: 11/18: ovirt-engine-dbscripts | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager | yumpackager.verbose:84 Yum Done: ovirt-engine-dbscripts-3.3.0-20.fc18.noarch | 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager | yumpackager.verbose:84 Yum Done: ovirt-engine-backend | Traceback (most recent call last): | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 464, in | callback | self._unInstStop( bytes, total, h ) | File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 564, in | _unInstStop | self.total_actions) | File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 204, in | event | package=package.name, | AttributeError: 'str' object has no attribute 'name' | FATAL ERROR: python callback > failed, aborting! | | To test the database upgrade I will revert to a previous snapshot of the | debug VM, capture the dbase from the previous engine version, re-run | upgrade, dump the upgraded database, restore the previous, and then test a | manual run of the database upgrade script. | | Does this sound prudent? | - DHC | Yes. Although lots of work, it may show if there's a DB upgrade bug we missed, or indeed the general upgrade procedure has / had an issue. | | On Tue, Jul 30, 2013 at 5:54 AM, Doron Fediuck wrote: | | > Thanks. | > So this leads me further to the upgrade procedure | > which may have fail, thus not completing the DB upgrade. | > Can you please check the upgrade logs to see if something | > matches this flow? | > | > - Original Message - | > | From: "Dead Horse" | > | To: "Doron Fediuck" | > | Cc: "Alon Bar-Lev" , "users" , | > "Dave Chen" , "Eli Mesika" | > | | > | Sent: Tuesday, July 30, 2013 6:37:55 AM | > | Subject: Re: [Users] upgrade to latest master not working | > | | > | The engine version I am attempting to upgrade from was built from: | > | --- | > | commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 | > | tree: ee9ee41c3e855c26f491c77fda9622c05af3fc54 | > | parent: 82644cae97f3c546ee631ae79c925c91e7bed836 | > | | > | userportal,webadmin: Change remove message | > | Change-Id: Ia934e33d1a975e0235e1a1ffae0c8a4a7af66f10 | > | Signed-off-by: Alexander Wels | > | --- | > | 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. | > | | > | - DHC | > | | > | | > | | > | On Mon, Jul 29, 2013 at 4:08 PM, Doron Fediuck | > wrote: | > | | > | > | > | > | > | > - Original Message - | > | > | From: "Alon Bar-Lev" | > | > | To: "Doron Fediuck" | > | > | Cc: "Dead Horse" , "users" < | > | > users@ovirt.org>, "Dave Chen" , "Eli | > | > | Mesika" | > | > | Sent: Monday, July 29, 2013 11:51:35 PM | > | > | Subject: Re: [Users] upgrade to latest master not working | > | > | | > | > | | > | > | | > | > | - Original Message - | > | > | > From: "Doron Fediuck" | > | > | > To: "Alon Bar-Lev" | > | > | > Cc: "Dead Horse" , "users" | > | > | > , "Dave Chen" , "Eli | > | > | > Mesika" | > | > | > Sent: Monday, July 29, 2013 11:43:46 PM | > | > | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > | > | > | > | > | > | > | > | > - Original Message - | > | > | > | From: "Alon Bar-Lev" | > | > | > | To: "Doro
Re: [Users] upgrade to latest master not working
The only error I can find in the upgrade log is: 2013-07-29 14:06:28 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u 2013-07-29 14:06:28 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:88 Yum update: 10/18: ovirt-engine 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:84 Yum Done: ovirt-engine.noarch 0:3.3.0-20.fc18 - u 2013-07-29 14:06:35 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:84 Yum Done: ovirt-engine-3.3.0-20.fc18.noarch 2013-07-29 14:06:37 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:88 Yum update: 11/18: ovirt-engine-dbscripts 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:84 Yum Done: ovirt-engine-dbscripts-3.3.0-20.fc18.noarch 2013-07-29 14:06:38 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:84 Yum Done: ovirt-engine-backend Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 464, in callback self._unInstStop( bytes, total, h ) File "/usr/lib/python2.7/site-packages/yum/rpmtrans.py", line 564, in _unInstStop self.total_actions) File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 204, in event package=package.name, AttributeError: 'str' object has no attribute 'name' FATAL ERROR: python callback > failed, aborting! To test the database upgrade I will revert to a previous snapshot of the debug VM, capture the dbase from the previous engine version, re-run upgrade, dump the upgraded database, restore the previous, and then test a manual run of the database upgrade script. Does this sound prudent? - DHC On Tue, Jul 30, 2013 at 5:54 AM, Doron Fediuck wrote: > Thanks. > So this leads me further to the upgrade procedure > which may have fail, thus not completing the DB upgrade. > Can you please check the upgrade logs to see if something > matches this flow? > > - Original Message - > | From: "Dead Horse" > | To: "Doron Fediuck" > | Cc: "Alon Bar-Lev" , "users" , > "Dave Chen" , "Eli Mesika" > | > | Sent: Tuesday, July 30, 2013 6:37:55 AM > | Subject: Re: [Users] upgrade to latest master not working > | > | The engine version I am attempting to upgrade from was built from: > | --- > | commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 > | tree: ee9ee41c3e855c26f491c77fda9622c05af3fc54 > | parent: 82644cae97f3c546ee631ae79c925c91e7bed836 > | > | userportal,webadmin: Change remove message > | Change-Id: Ia934e33d1a975e0235e1a1ffae0c8a4a7af66f10 > | Signed-off-by: Alexander Wels > | --- > | 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. > | > | - DHC > | > | > | > | On Mon, Jul 29, 2013 at 4:08 PM, Doron Fediuck > wrote: > | > | > > | > > | > - Original Message - > | > | From: "Alon Bar-Lev" > | > | To: "Doron Fediuck" > | > | Cc: "Dead Horse" , "users" < > | > users@ovirt.org>, "Dave Chen" , "Eli > | > | Mesika" > | > | Sent: Monday, July 29, 2013 11:51:35 PM > | > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | > | > | > | > | - Original Message - > | > | > From: "Doron Fediuck" > | > | > To: "Alon Bar-Lev" > | > | > Cc: "Dead Horse" , "users" > | > | > , "Dave Chen" , "Eli > | > | > Mesika" > | > | > Sent: Monday, July 29, 2013 11:43:46 PM > | > | > Subject: Re: [Users] upgrade to latest master not working > | > | > > | > | > > | > | > > | > | > - Original Message - > | > | > | From: "Alon Bar-Lev" > | > | > | To: "Doron Fediuck" > | > | > | Cc: "Dead Horse" , "users" > | > | > | , "Dave Chen" , "Eli > | > | > | Mesika" > | > | > | Sent: Monday, July 29, 2013 11:31:42 PM > | > | > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | > | > | > | > | > | > | > | > | - Original Message - > | > | > | > From: "Doron Fediuck" > | > | > | > To: "Alon Bar-Lev" > | > | > | > Cc: "Dead Horse" , "users" > | > | > | > , "Dave Chen&
Re: [Users] upgrade to latest master not working
Thanks. So this leads me further to the upgrade procedure which may have fail, thus not completing the DB upgrade. Can you please check the upgrade logs to see if something matches this flow? - Original Message - | From: "Dead Horse" | To: "Doron Fediuck" | Cc: "Alon Bar-Lev" , "users" , "Dave Chen" , "Eli Mesika" | | Sent: Tuesday, July 30, 2013 6:37:55 AM | Subject: Re: [Users] upgrade to latest master not working | | The engine version I am attempting to upgrade from was built from: | --- | commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 | tree: ee9ee41c3e855c26f491c77fda9622c05af3fc54 | parent: 82644cae97f3c546ee631ae79c925c91e7bed836 | | userportal,webadmin: Change remove message | Change-Id: Ia934e33d1a975e0235e1a1ffae0c8a4a7af66f10 | Signed-off-by: Alexander Wels | --- | 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. | | - DHC | | | | On Mon, Jul 29, 2013 at 4:08 PM, Doron Fediuck wrote: | | > | > | > - Original Message - | > | From: "Alon Bar-Lev" | > | To: "Doron Fediuck" | > | Cc: "Dead Horse" , "users" < | > users@ovirt.org>, "Dave Chen" , "Eli | > | Mesika" | > | Sent: Monday, July 29, 2013 11:51:35 PM | > | Subject: Re: [Users] upgrade to latest master not working | > | | > | | > | | > | - Original Message - | > | > From: "Doron Fediuck" | > | > To: "Alon Bar-Lev" | > | > Cc: "Dead Horse" , "users" | > | > , "Dave Chen" , "Eli | > | > Mesika" | > | > Sent: Monday, July 29, 2013 11:43:46 PM | > | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > | > | > | > | > ----- Original Message - | > | > | From: "Alon Bar-Lev" | > | > | To: "Doron Fediuck" | > | > | Cc: "Dead Horse" , "users" | > | > | , "Dave Chen" , "Eli | > | > | Mesika" | > | > | Sent: Monday, July 29, 2013 11:31:42 PM | > | > | Subject: Re: [Users] upgrade to latest master not working | > | > | | > | > | | > | > | | > | > | - Original Message - | > | > | > From: "Doron Fediuck" | > | > | > To: "Alon Bar-Lev" | > | > | > Cc: "Dead Horse" , "users" | > | > | > , "Dave Chen" , "Eli | > | > | > Mesika" | > | > | > Sent: Monday, July 29, 2013 11:27:41 PM | > | > | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > | > | > | > | > | > | > | > | > - Original Message - | > | > | > | From: "Alon Bar-Lev" | > | > | > | To: "Dead Horse" | > | > | > | Cc: "users" , "Doron Fediuck" < | > dfedi...@redhat.com>, | > | > | > | "Dave | > | > | > | Chen" , "Eli | > | > | > | Mesika" | > | > | > | Sent: Monday, July 29, 2013 10:47:01 PM | > | > | > | Subject: Re: [Users] upgrade to latest master not working | > | > | > | | > | > | > | | > | > | > | | > | > | > | - Original Message - | > | > | > | > From: "Dead Horse" | > | > | > | > To: "Alon Bar-Lev" | > | > | > | > Cc: "users" | > | > | > | > Sent: Monday, July 29, 2013 10:41:34 PM | > | > | > | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > | > | > | > | > server.log attached | > | > | > | | > | > | > | Thanks! | > | > | > | | > | > | > | My guess is that I8ce3448a[1] broke master. | > | > | > | | > | > | > | [1] http://gerrit.ovirt.org/#/c/14605/ | > | > | > | | > | > | > | > | > | > Works perfectly on my Gentoo with master. | > | > | > | > | > | | > | > | I doubt you are upgrading from 3.2 :) | > | > | | > | > | > | > Just did: | > | > | > | > $ git checkout origin/engine_3.2 | > | > $ cd backend/manager/dbscripts/ | > | > $ ./create_db.sh -d upgrade32-test -u engine | > | > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts | > | > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts | > | > Creating the database: upgrade32-test | > | > dropdb: database removal failed: ERROR: database "upgrade32-test" | > does not
Re: [Users] upgrade to latest master not working
The engine version I am attempting to upgrade from was built from: --- commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 tree: ee9ee41c3e855c26f491c77fda9622c05af3fc54 parent: 82644cae97f3c546ee631ae79c925c91e7bed836 userportal,webadmin: Change remove message Change-Id: Ia934e33d1a975e0235e1a1ffae0c8a4a7af66f10 Signed-off-by: Alexander Wels --- 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. - DHC On Mon, Jul 29, 2013 at 4:08 PM, Doron Fediuck wrote: > > > - Original Message - > | From: "Alon Bar-Lev" > | To: "Doron Fediuck" > | Cc: "Dead Horse" , "users" < > users@ovirt.org>, "Dave Chen" , "Eli > | Mesika" > | Sent: Monday, July 29, 2013 11:51:35 PM > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | - Original Message - > | > From: "Doron Fediuck" > | > To: "Alon Bar-Lev" > | > Cc: "Dead Horse" , "users" > | > , "Dave Chen" , "Eli > | > Mesika" > | > Sent: Monday, July 29, 2013 11:43:46 PM > | > Subject: Re: [Users] upgrade to latest master not working > | > > | > > | > > | > - Original Message - > | > | From: "Alon Bar-Lev" > | > | To: "Doron Fediuck" > | > | Cc: "Dead Horse" , "users" > | > | , "Dave Chen" , "Eli > | > | Mesika" > | > | Sent: Monday, July 29, 2013 11:31:42 PM > | > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | > | > | > | > | - Original Message - > | > | > From: "Doron Fediuck" > | > | > To: "Alon Bar-Lev" > | > | > Cc: "Dead Horse" , "users" > | > | > , "Dave Chen" , "Eli > | > | > Mesika" > | > | > Sent: Monday, July 29, 2013 11:27:41 PM > | > | > Subject: Re: [Users] upgrade to latest master not working > | > | > > | > | > > | > | > > | > | > - Original Message - > | > | > | From: "Alon Bar-Lev" > | > | > | To: "Dead Horse" > | > | > | Cc: "users" , "Doron Fediuck" < > dfedi...@redhat.com>, > | > | > | "Dave > | > | > | Chen" , "Eli > | > | > | Mesika" > | > | > | Sent: Monday, July 29, 2013 10:47:01 PM > | > | > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | > | > | > | > | > | > | > | > | - Original Message - > | > | > | > From: "Dead Horse" > | > | > | > To: "Alon Bar-Lev" > | > | > | > Cc: "users" > | > | > | > Sent: Monday, July 29, 2013 10:41:34 PM > | > | > | > Subject: Re: [Users] upgrade to latest master not working > | > | > | > > | > | > | > server.log attached > | > | > | > | > | > | Thanks! > | > | > | > | > | > | My guess is that I8ce3448a[1] broke master. > | > | > | > | > | > | [1] http://gerrit.ovirt.org/#/c/14605/ > | > | > | > | > | > > | > | > Works perfectly on my Gentoo with master. > | > | > > | > | > | > | I doubt you are upgrading from 3.2 :) > | > | > | > > | > Just did: > | > > | > $ git checkout origin/engine_3.2 > | > $ cd backend/manager/dbscripts/ > | > $ ./create_db.sh -d upgrade32-test -u engine > | > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts > | > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts > | > Creating the database: upgrade32-test > | > dropdb: database removal failed: ERROR: database "upgrade32-test" > does not > | > exist > | > user name is: engine > | > Creating tables... > | > Creating functions... > | > Creating common functions... > | > Inserting data ... > | > Inserting pre-defined roles ... > | > Running upgrade scripts... > | > upgrade script detected a change in Config, View or Stored Procedure... > | > Running upgrade sql script upgrade/pre_upgrade/_config.sql ... > | > > | > ... > | > > | > Creating stored procedures from vm_templates_sp.sql ... > | > Running upgrade sql script > | > upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ... > | > Running upgrade sql script > | &g
Re: [Users] upgrade to latest master not working
- Original Message - | From: "Alon Bar-Lev" | To: "Doron Fediuck" | Cc: "Dead Horse" , "users" , "Dave Chen" , "Eli | Mesika" | Sent: Monday, July 29, 2013 11:51:35 PM | Subject: Re: [Users] upgrade to latest master not working | | | | - Original Message - | > From: "Doron Fediuck" | > To: "Alon Bar-Lev" | > Cc: "Dead Horse" , "users" | > , "Dave Chen" , "Eli | > Mesika" | > Sent: Monday, July 29, 2013 11:43:46 PM | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > - Original Message - | > | From: "Alon Bar-Lev" | > | To: "Doron Fediuck" | > | Cc: "Dead Horse" , "users" | > | , "Dave Chen" , "Eli | > | Mesika" | > | Sent: Monday, July 29, 2013 11:31:42 PM | > | Subject: Re: [Users] upgrade to latest master not working | > | | > | | > | | > | - Original Message ----- | > | > From: "Doron Fediuck" | > | > To: "Alon Bar-Lev" | > | > Cc: "Dead Horse" , "users" | > | > , "Dave Chen" , "Eli | > | > Mesika" | > | > Sent: Monday, July 29, 2013 11:27:41 PM | > | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > | > | > | > | > - Original Message - | > | > | From: "Alon Bar-Lev" | > | > | To: "Dead Horse" | > | > | Cc: "users" , "Doron Fediuck" , | > | > | "Dave | > | > | Chen" , "Eli | > | > | Mesika" | > | > | Sent: Monday, July 29, 2013 10:47:01 PM | > | > | Subject: Re: [Users] upgrade to latest master not working | > | > | | > | > | | > | > | | > | > | - Original Message - | > | > | > From: "Dead Horse" | > | > | > To: "Alon Bar-Lev" | > | > | > Cc: "users" | > | > | > Sent: Monday, July 29, 2013 10:41:34 PM | > | > | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > | > | > server.log attached | > | > | | > | > | Thanks! | > | > | | > | > | My guess is that I8ce3448a[1] broke master. | > | > | | > | > | [1] http://gerrit.ovirt.org/#/c/14605/ | > | > | | > | > | > | > Works perfectly on my Gentoo with master. | > | > | > | | > | I doubt you are upgrading from 3.2 :) | > | | > | > Just did: | > | > $ git checkout origin/engine_3.2 | > $ cd backend/manager/dbscripts/ | > $ ./create_db.sh -d upgrade32-test -u engine | > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts | > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts | > Creating the database: upgrade32-test | > dropdb: database removal failed: ERROR: database "upgrade32-test" does not | > exist | > user name is: engine | > Creating tables... | > Creating functions... | > Creating common functions... | > Inserting data ... | > Inserting pre-defined roles ... | > Running upgrade scripts... | > upgrade script detected a change in Config, View or Stored Procedure... | > Running upgrade sql script upgrade/pre_upgrade/_config.sql ... | > | > ... | > | > Creating stored procedures from vm_templates_sp.sql ... | > Running upgrade sql script | > upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ... | > Running upgrade sql script | > upgrade/post_upgrade/0020_create_materialized_views.sql ... | > Refreshing materialized views... | > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts | > | > $ git checkout master | > $ cd ../../../packaging/dbscripts/ | > $ ./upgrade.sh -d upgrade32-test -u engine | > upgrade script detected a change in Config, View or Stored Procedure... | > Running upgrade sql script upgrade/pre_upgrade/_config.sql ... | > | > ... | > | > Creating stored procedures from vms_sp.sql ... | > Running upgrade sql script | > upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ... | > Running upgrade sql script | > upgrade/post_upgrade/0020_create_materialized_views.sql ... | > Refreshing materialized views... | > Done. | > | > | > Seems to work well. Am I missing something? | > | | Start jboss? | | Please take over this issue, you have relevant logs, and a cooperative user. | | Thanks, | Alon | Since jboss is up and running very well after upgrade I do not see a problem. Is it possible that the install / upgrade process didn't complete due to other errors ending up with this state? In the meantime you can manually create the missing function to get your setup running. The only problem is that if my assumption is correct on upgrade not finishing, you will hit the next db change as an error. So I'd try and look at the install/upgrade log files to see if db upgrade failed at some point. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] upgrade to latest master not working
- Original Message - > From: "Doron Fediuck" > To: "Alon Bar-Lev" > Cc: "Dead Horse" , "users" , > "Dave Chen" , "Eli > Mesika" > Sent: Monday, July 29, 2013 11:43:46 PM > Subject: Re: [Users] upgrade to latest master not working > > > > - Original Message - > | From: "Alon Bar-Lev" > | To: "Doron Fediuck" > | Cc: "Dead Horse" , "users" > | , "Dave Chen" , "Eli > | Mesika" > | Sent: Monday, July 29, 2013 11:31:42 PM > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | - Original Message - > | > From: "Doron Fediuck" > | > To: "Alon Bar-Lev" > | > Cc: "Dead Horse" , "users" > | > , "Dave Chen" , "Eli > | > Mesika" > | > Sent: Monday, July 29, 2013 11:27:41 PM > | > Subject: Re: [Users] upgrade to latest master not working > | > > | > > | > > | > - Original Message - > | > | From: "Alon Bar-Lev" > | > | To: "Dead Horse" > | > | Cc: "users" , "Doron Fediuck" , > | > | "Dave > | > | Chen" , "Eli > | > | Mesika" > | > | Sent: Monday, July 29, 2013 10:47:01 PM > | > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | > | > | > | > | - Original Message - > | > | > From: "Dead Horse" > | > | > To: "Alon Bar-Lev" > | > | > Cc: "users" > | > | > Sent: Monday, July 29, 2013 10:41:34 PM > | > | > Subject: Re: [Users] upgrade to latest master not working > | > | > > | > | > server.log attached > | > | > | > | Thanks! > | > | > | > | My guess is that I8ce3448a[1] broke master. > | > | > | > | [1] http://gerrit.ovirt.org/#/c/14605/ > | > | > | > > | > Works perfectly on my Gentoo with master. > | > > | > | I doubt you are upgrading from 3.2 :) > | > > Just did: > > $ git checkout origin/engine_3.2 > $ cd backend/manager/dbscripts/ > $ ./create_db.sh -d upgrade32-test -u engine > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts > Creating the database: upgrade32-test > dropdb: database removal failed: ERROR: database "upgrade32-test" does not > exist > user name is: engine > Creating tables... > Creating functions... > Creating common functions... > Inserting data ... > Inserting pre-defined roles ... > Running upgrade scripts... > upgrade script detected a change in Config, View or Stored Procedure... > Running upgrade sql script upgrade/pre_upgrade/_config.sql ... > > ... > > Creating stored procedures from vm_templates_sp.sql ... > Running upgrade sql script > upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ... > Running upgrade sql script > upgrade/post_upgrade/0020_create_materialized_views.sql ... > Refreshing materialized views... > ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts > > $ git checkout master > $ cd ../../../packaging/dbscripts/ > $ ./upgrade.sh -d upgrade32-test -u engine > upgrade script detected a change in Config, View or Stored Procedure... > Running upgrade sql script upgrade/pre_upgrade/_config.sql ... > > ... > > Creating stored procedures from vms_sp.sql ... > Running upgrade sql script > upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ... > Running upgrade sql script > upgrade/post_upgrade/0020_create_materialized_views.sql ... > Refreshing materialized views... > Done. > > > Seems to work well. Am I missing something? > Start jboss? Please take over this issue, you have relevant logs, and a cooperative user. Thanks, Alon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] upgrade to latest master not working
- Original Message - | From: "Alon Bar-Lev" | To: "Doron Fediuck" | Cc: "Dead Horse" , "users" , "Dave Chen" , "Eli | Mesika" | Sent: Monday, July 29, 2013 11:31:42 PM | Subject: Re: [Users] upgrade to latest master not working | | | | - Original Message - | > From: "Doron Fediuck" | > To: "Alon Bar-Lev" | > Cc: "Dead Horse" , "users" | > , "Dave Chen" , "Eli | > Mesika" | > Sent: Monday, July 29, 2013 11:27:41 PM | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > - Original Message - | > | From: "Alon Bar-Lev" | > | To: "Dead Horse" | > | Cc: "users" , "Doron Fediuck" , | > | "Dave | > | Chen" , "Eli | > | Mesika" | > | Sent: Monday, July 29, 2013 10:47:01 PM | > | Subject: Re: [Users] upgrade to latest master not working | > | | > | | > | | > | - Original Message - | > | > From: "Dead Horse" | > | > To: "Alon Bar-Lev" | > | > Cc: "users" | > | > Sent: Monday, July 29, 2013 10:41:34 PM | > | > Subject: Re: [Users] upgrade to latest master not working | > | > | > | > server.log attached | > | | > | Thanks! | > | | > | My guess is that I8ce3448a[1] broke master. | > | | > | [1] http://gerrit.ovirt.org/#/c/14605/ | > | | > | > Works perfectly on my Gentoo with master. | > | | I doubt you are upgrading from 3.2 :) | Just did: $ git checkout origin/engine_3.2 $ cd backend/manager/dbscripts/ $ ./create_db.sh -d upgrade32-test -u engine ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts Creating the database: upgrade32-test dropdb: database removal failed: ERROR: database "upgrade32-test" does not exist user name is: engine Creating tables... Creating functions... Creating common functions... Inserting data ... Inserting pre-defined roles ... Running upgrade scripts... upgrade script detected a change in Config, View or Stored Procedure... Running upgrade sql script upgrade/pre_upgrade/_config.sql ... ... Creating stored procedures from vm_templates_sp.sql ... Running upgrade sql script upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ... Running upgrade sql script upgrade/post_upgrade/0020_create_materialized_views.sql ... Refreshing materialized views... ~/dev/ovirt/ovirt-engine/backend/manager/dbscripts $ git checkout master $ cd ../../../packaging/dbscripts/ $ ./upgrade.sh -d upgrade32-test -u engine upgrade script detected a change in Config, View or Stored Procedure... Running upgrade sql script upgrade/pre_upgrade/_config.sql ... ... Creating stored procedures from vms_sp.sql ... Running upgrade sql script upgrade/post_upgrade/0010_add_object_column_white_list_table.sql ... Running upgrade sql script upgrade/post_upgrade/0020_create_materialized_views.sql ... Refreshing materialized views... Done. Seems to work well. Am I missing something? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] upgrade to latest master not working
- Original Message - > From: "Doron Fediuck" > To: "Alon Bar-Lev" > Cc: "Dead Horse" , "users" , > "Dave Chen" , "Eli > Mesika" > Sent: Monday, July 29, 2013 11:27:41 PM > Subject: Re: [Users] upgrade to latest master not working > > > > - Original Message - > | From: "Alon Bar-Lev" > | To: "Dead Horse" > | Cc: "users" , "Doron Fediuck" , "Dave > | Chen" , "Eli > | Mesika" > | Sent: Monday, July 29, 2013 10:47:01 PM > | Subject: Re: [Users] upgrade to latest master not working > | > | > | > | - Original Message - > | > From: "Dead Horse" > | > To: "Alon Bar-Lev" > | > Cc: "users" > | > Sent: Monday, July 29, 2013 10:41:34 PM > | > Subject: Re: [Users] upgrade to latest master not working > | > > | > server.log attached > | > | Thanks! > | > | My guess is that I8ce3448a[1] broke master. > | > | [1] http://gerrit.ovirt.org/#/c/14605/ > | > > Works perfectly on my Gentoo with master. > I doubt you are upgrading from 3.2 :) > | > > | > > | > On Mon, Jul 29, 2013 at 2:30 PM, Alon Bar-Lev wrote: > | > > | > > > | > > > | > > - Original Message - > | > > > From: "Dead Horse" > | > > > To: "Alon Bar-Lev" > | > > > Cc: "users" > | > > > Sent: Monday, July 29, 2013 10:19:45 PM > | > > > Subject: Re: [Users] upgrade to latest master not working > | > > > > | > > > That patch fixed that issue, (re-tested with build from master this > | > > > AM) > | > > and > | > > > the upgrade proceeded. > | > > > > | > > > However after the upgrade the engine.ear deployment to jboss is > | > > > failing. > | > > > (log files attached) > | > > > - DHC > | > > > | > > This is not good... can you please attach server.log? > | > > > | > > > > | > > > > | > > > On Sat, Jul 27, 2013 at 1:28 AM, Alon Bar-Lev > | > > > wrote: > | > > > > | > > > > > | > > > > > | > > > > - Original Message - > | > > > > > From: "Dead Horse" > | > > > > > To: "Alon Bar-Lev" > | > > > > > Cc: "users" > | > > > > > Sent: Saturday, July 27, 2013 2:05:08 AM > | > > > > > Subject: Re: [Users] upgrade to latest master not working > | > > > > > > | > > > > > Yep there was a leftover: > | > > > > > > | > > /usr/share/ovirt-engine/setup/plugins/ovirt-engine-setup/releasepreview > | > > > > > > | > > > > > I got past that now however it is now failing at the Environment > | > > > > > customization stage. > | > > > > > > | > > > > > Here is the output of engine-upgrade. I have also attached the > | > > upgrade > | > > > > log. > | > > > > > > | > > > > > [ INFO ] Stage: Initializing > | > > > > > [ INFO ] Stage: Environment setup > | > > > > > Log file: /tmp/ovirt-engine-setup-20130726175419.log > | > > > > > Version: otopi-3.3.020 > | > > > > > Configuration files: > | > > > > > ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf'] > | > > > > > [ INFO ] Stage: Environment packages setup > | > > > > > [ INFO ] Stage: Programs detection > | > > > > > [ INFO ] Stage: Environment setup > | > > > > > [ INFO ] Stage: Environment customization > | > > > > > [ ERROR ] Failed to execute stage 'Environment customization': > | > > > > > Cannot > | > > > > > connect to database: server does not support SSL, but SSL was > | > > required > | > > > > > [ INFO ] Stage: Clean up > | > > > > > Log file is located at > | > > > > /tmp/ovirt-engine-setup-20130726175419.log > | > > > > > [ INFO ] Stage: Pre-termination > | > > > > > [ INFO ] Stage: Termination > | > > > > > > | > > > > > - DHC > | > > > > > | > > > > Correct, thanks! > | > > > > I prepared a
Re: [Users] upgrade to latest master not working
- Original Message - | From: "Alon Bar-Lev" | To: "Dead Horse" | Cc: "users" , "Doron Fediuck" , "Dave Chen" , "Eli | Mesika" | Sent: Monday, July 29, 2013 10:47:01 PM | Subject: Re: [Users] upgrade to latest master not working | | | | - Original Message - | > From: "Dead Horse" | > To: "Alon Bar-Lev" | > Cc: "users" | > Sent: Monday, July 29, 2013 10:41:34 PM | > Subject: Re: [Users] upgrade to latest master not working | > | > server.log attached | | Thanks! | | My guess is that I8ce3448a[1] broke master. | | [1] http://gerrit.ovirt.org/#/c/14605/ | Works perfectly on my Gentoo with master. | > | > | > On Mon, Jul 29, 2013 at 2:30 PM, Alon Bar-Lev wrote: | > | > > | > > | > > - Original Message - | > > > From: "Dead Horse" | > > > To: "Alon Bar-Lev" | > > > Cc: "users" | > > > Sent: Monday, July 29, 2013 10:19:45 PM | > > > Subject: Re: [Users] upgrade to latest master not working | > > > | > > > That patch fixed that issue, (re-tested with build from master this AM) | > > and | > > > the upgrade proceeded. | > > > | > > > However after the upgrade the engine.ear deployment to jboss is | > > > failing. | > > > (log files attached) | > > > - DHC | > > | > > This is not good... can you please attach server.log? | > > | > > > | > > > | > > > On Sat, Jul 27, 2013 at 1:28 AM, Alon Bar-Lev | > > > wrote: | > > > | > > > > | > > > > | > > > > - Original Message - | > > > > > From: "Dead Horse" | > > > > > To: "Alon Bar-Lev" | > > > > > Cc: "users" | > > > > > Sent: Saturday, July 27, 2013 2:05:08 AM | > > > > > Subject: Re: [Users] upgrade to latest master not working | > > > > > | > > > > > Yep there was a leftover: | > > > > > | > > /usr/share/ovirt-engine/setup/plugins/ovirt-engine-setup/releasepreview | > > > > > | > > > > > I got past that now however it is now failing at the Environment | > > > > > customization stage. | > > > > > | > > > > > Here is the output of engine-upgrade. I have also attached the | > > upgrade | > > > > log. | > > > > > | > > > > > [ INFO ] Stage: Initializing | > > > > > [ INFO ] Stage: Environment setup | > > > > > Log file: /tmp/ovirt-engine-setup-20130726175419.log | > > > > > Version: otopi-3.3.020 | > > > > > Configuration files: | > > > > > ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf'] | > > > > > [ INFO ] Stage: Environment packages setup | > > > > > [ INFO ] Stage: Programs detection | > > > > > [ INFO ] Stage: Environment setup | > > > > > [ INFO ] Stage: Environment customization | > > > > > [ ERROR ] Failed to execute stage 'Environment customization': | > > > > > Cannot | > > > > > connect to database: server does not support SSL, but SSL was | > > required | > > > > > [ INFO ] Stage: Clean up | > > > > > Log file is located at | > > > > /tmp/ovirt-engine-setup-20130726175419.log | > > > > > [ INFO ] Stage: Pre-termination | > > > > > [ INFO ] Stage: Termination | > > > > > | > > > > > - DHC | > > > > | > > > > Correct, thanks! | > > > > I prepared a patch[1]. | > > > > | > > > > commit 18fe8cf53c519fdb8a4e831faf3b0a6c5a64167b | > > > > Author: Alon Bar-Lev | > > > > Date: Sat Jul 27 09:25:27 2013 +0300 | > > > > | > > > > packaging: setup: legacy: ssl flags should be boolean | > > > > | > > > > Change-Id: I9bc9f59a2a3ac18f613200bf2f9b70948b494b91 | > > > > Signed-off-by: Alon Bar-Lev | > > > > Reported-By: Dead Horse | > > > > | > > > > [1] http://gerrit.ovirt.org/17359 | > > > > | > > > > > | > > > > > | > > > > > | > > > > > On Fri, Jul 26, 2013 at 3:38 PM, Alon Bar-Lev | > > wrote: | > > &g
Re: [Users] upgrade to latest master not working
- Original Message - > From: "Dead Horse" > To: "Alon Bar-Lev" > Cc: "users" > Sent: Monday, July 29, 2013 10:19:45 PM > Subject: Re: [Users] upgrade to latest master not working > > That patch fixed that issue, (re-tested with build from master this AM) and > the upgrade proceeded. > > However after the upgrade the engine.ear deployment to jboss is failing. > (log files attached) > - DHC This is not good... can you please attach server.log? > > > On Sat, Jul 27, 2013 at 1:28 AM, Alon Bar-Lev wrote: > > > > > > > - Original Message - > > > From: "Dead Horse" > > > To: "Alon Bar-Lev" > > > Cc: "users" > > > Sent: Saturday, July 27, 2013 2:05:08 AM > > > Subject: Re: [Users] upgrade to latest master not working > > > > > > Yep there was a leftover: > > > /usr/share/ovirt-engine/setup/plugins/ovirt-engine-setup/releasepreview > > > > > > I got past that now however it is now failing at the Environment > > > customization stage. > > > > > > Here is the output of engine-upgrade. I have also attached the upgrade > > log. > > > > > > [ INFO ] Stage: Initializing > > > [ INFO ] Stage: Environment setup > > > Log file: /tmp/ovirt-engine-setup-20130726175419.log > > > Version: otopi-3.3.020 > > > Configuration files: > > > ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf'] > > > [ INFO ] Stage: Environment packages setup > > > [ INFO ] Stage: Programs detection > > > [ INFO ] Stage: Environment setup > > > [ INFO ] Stage: Environment customization > > > [ ERROR ] Failed to execute stage 'Environment customization': Cannot > > > connect to database: server does not support SSL, but SSL was required > > > [ INFO ] Stage: Clean up > > > Log file is located at > > /tmp/ovirt-engine-setup-20130726175419.log > > > [ INFO ] Stage: Pre-termination > > > [ INFO ] Stage: Termination > > > > > > - DHC > > > > Correct, thanks! > > I prepared a patch[1]. > > > > commit 18fe8cf53c519fdb8a4e831faf3b0a6c5a64167b > > Author: Alon Bar-Lev > > Date: Sat Jul 27 09:25:27 2013 +0300 > > > > packaging: setup: legacy: ssl flags should be boolean > > > > Change-Id: I9bc9f59a2a3ac18f613200bf2f9b70948b494b91 > > Signed-off-by: Alon Bar-Lev > > Reported-By: Dead Horse > > > > [1] http://gerrit.ovirt.org/17359 > > > > > > > > > > > > > > On Fri, Jul 26, 2013 at 3:38 PM, Alon Bar-Lev wrote: > > > > > > > > > > > You probably have some leftovers at /usr/share/ovirt-engine/setup, > > search > > > > for releasepreview > > > > > > > > - Original Message - > > > > > From: "Dead Horse" > > > > > To: "" > > > > > Sent: Friday, July 26, 2013 11:34:09 PM > > > > > Subject: [Users] upgrade to latest master not working > > > > > > > > > > Trying to upgrade engine built from > > > > > commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 > > > > > > > > > > To latest engine built from latest master > > > > > > > > > > running engine-upgrade results in: > > > > > > > > > > ***L:ERROR Internal Error: No Module named releasepreview > > > > > > > > > > I know I must be missing something obvious? > > > > > > > > > > The surrounding versions of otopi, host-deploy, etc do yum upgrade > > > > cleanly > > > > > however. > > > > > > > > > > - DHC > > > > > > > > > > ___ > > > > > Users mailing list > > > > > Users@ovirt.org > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] upgrade to latest master not working
- Original Message - > From: "Dead Horse" > To: "Alon Bar-Lev" > Cc: "users" > Sent: Saturday, July 27, 2013 2:05:08 AM > Subject: Re: [Users] upgrade to latest master not working > > Yep there was a leftover: > /usr/share/ovirt-engine/setup/plugins/ovirt-engine-setup/releasepreview > > I got past that now however it is now failing at the Environment > customization stage. > > Here is the output of engine-upgrade. I have also attached the upgrade log. > > [ INFO ] Stage: Initializing > [ INFO ] Stage: Environment setup > Log file: /tmp/ovirt-engine-setup-20130726175419.log > Version: otopi-3.3.020 > Configuration files: > ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf'] > [ INFO ] Stage: Environment packages setup > [ INFO ] Stage: Programs detection > [ INFO ] Stage: Environment setup > [ INFO ] Stage: Environment customization > [ ERROR ] Failed to execute stage 'Environment customization': Cannot > connect to database: server does not support SSL, but SSL was required > [ INFO ] Stage: Clean up > Log file is located at /tmp/ovirt-engine-setup-20130726175419.log > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > > - DHC Correct, thanks! I prepared a patch[1]. commit 18fe8cf53c519fdb8a4e831faf3b0a6c5a64167b Author: Alon Bar-Lev Date: Sat Jul 27 09:25:27 2013 +0300 packaging: setup: legacy: ssl flags should be boolean Change-Id: I9bc9f59a2a3ac18f613200bf2f9b70948b494b91 Signed-off-by: Alon Bar-Lev Reported-By: Dead Horse [1] http://gerrit.ovirt.org/17359 > > > > On Fri, Jul 26, 2013 at 3:38 PM, Alon Bar-Lev wrote: > > > > > You probably have some leftovers at /usr/share/ovirt-engine/setup, search > > for releasepreview > > > > - Original Message - > > > From: "Dead Horse" > > > To: "" > > > Sent: Friday, July 26, 2013 11:34:09 PM > > > Subject: [Users] upgrade to latest master not working > > > > > > Trying to upgrade engine built from > > > commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 > > > > > > To latest engine built from latest master > > > > > > running engine-upgrade results in: > > > > > > ***L:ERROR Internal Error: No Module named releasepreview > > > > > > I know I must be missing something obvious? > > > > > > The surrounding versions of otopi, host-deploy, etc do yum upgrade > > cleanly > > > however. > > > > > > - DHC > > > > > > ___ > > > Users mailing list > > > Users@ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] upgrade to latest master not working
You probably have some leftovers at /usr/share/ovirt-engine/setup, search for releasepreview - Original Message - > From: "Dead Horse" > To: "" > Sent: Friday, July 26, 2013 11:34:09 PM > Subject: [Users] upgrade to latest master not working > > Trying to upgrade engine built from > commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 > > To latest engine built from latest master > > running engine-upgrade results in: > > ***L:ERROR Internal Error: No Module named releasepreview > > I know I must be missing something obvious? > > The surrounding versions of otopi, host-deploy, etc do yum upgrade cleanly > however. > > - DHC > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] upgrade to latest master not working
Trying to upgrade engine built from commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679 To latest engine built from latest master running engine-upgrade results in: ***L:ERROR Internal Error: No Module named releasepreview I know I must be missing something obvious? The surrounding versions of otopi, host-deploy, etc do yum upgrade cleanly however. - DHC ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
