Re: [ovirt-users] engine upgrade 3.2.2 --> 3.2.3 Database rename failed (Solved)
- Original Message - > From: "Neil" > To: "Sven Kieske" , "Juan Antonio Hernandez Fernandez" > > Cc: "Juergen Gotteswinter" , users@ovirt.org > Sent: Friday, May 23, 2014 11:22:53 AM > Subject: Re: [ovirt-users] engine upgrade 3.2.2 --> 3.2.3 Database rename > failed (Solved) > > Hi guys, > > I've managed to resolve this problem. Firstly after doing my fresh > re-install of my original rollback of Dreyou 3.2.2 ovirt-engine > re-install I hadn't run engine-cleanup, and then when I restored my DB > I used the "restore.sh -u postgres -f /root/ovirt.sql" instead of > doing a manual db restore which between the two of them got rid of the > issue. I'm assuming it was the engine-cleanup that sorted out the db > renaming problem though. > > Once that was done I then managed to upgrade to 3.3 and I'll now do > the 3.4 upgrade. Hi Keep in mind that backup.sh/restore.sh are obsolete in 3.4 and you should use engine-backup utility from now on... Thanks Eli Mesika > > Thanks very much for those who assisted. > > Regards. > > Neil Wilson. > > On Thu, May 22, 2014 at 6:12 AM, Neil wrote: > > Hi guys, sorry to repost but getting a bit desperate. Is anyone able to > > assist? > > > > Thanks. > > > > Regards. > > > > Neil Wilson > > > > On 21 May 2014 12:06 PM, "Neil" wrote: > >> > >> Hi guys, > >> > >> Just a little more info on the problem. I've upgraded another oVirt > >> system before from Dreyou and it worked perfectly, however on this > >> particular system, we had to restore from backups (DB PKI and > >> etc/ovirt-engine) as the physical machine died that was hosting the > >> engine, so perhaps this is the reason we encountering this problem > >> this time around... > >> > >> Any help is greatly appreciated. > >> > >> Thank you. > >> > >> Regards. > >> > >> Neil Wilson. > >> > >> > >> > >> On Wed, May 21, 2014 at 11:46 AM, Sven Kieske > >> wrote: > >> > Hi, > >> > > >> > I don't know the exact resolution for this, but I'll add some people > >> > who managed to make it work, following this tutorial: > >> > http://wiki.dreyou.org/dokuwiki/doku.php?id=ovirt_rpm_start33 > >> > > >> > See this thread on the users ML: > >> > > >> > http://lists.ovirt.org/pipermail/users/2013-December/018341.html > >> > > >> > HTH > >> > > >> > > >> > Am 20.05.2014 17:00, schrieb Neil: > >> >> Hi guys, > >> >> > >> >> I'm trying to upgrade from Dreyou to the official repo, I've installed > >> >> the official 3.2 repo (I'll do the 3.3 update once this works). I've > >> >> updated to ovirt-engine-setup.noarch 0:3.2.3-1.el6 and when I run > >> >> engine upgrade it bombs out when trying to rename my database with the > >> >> following error... > >> >> > >> >> [root@engine01 /]# cat > >> >> /var/log/ovirt-engine/ovirt-engine-upgrade_2014_05_20_16_34_21.log > >> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing > >> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB host value > >> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing > >> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB port value > >> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing > >> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB user value > >> >> 2014-05-20 16:34:21::DEBUG::common_utils::332::root:: YUM: VERB: > >> >> Loaded plugins: refresh-packagekit, versionlock > >> >> 2014-05-20 16:34:21::INFO::engine-upgrade::969::root:: Info: > >> >> /etc/ovirt-engine/.pgpass file found. Continue. > >> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing > >> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB admin value > >> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing > >> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB host value > >> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing > >> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB port value > >> >> 2014-05-20
Re: [ovirt-users] engine upgrade 3.2.2 --> 3.2.3 Database rename failed (Solved)
Hi guys,
I've managed to resolve this problem. Firstly after doing my fresh
re-install of my original rollback of Dreyou 3.2.2 ovirt-engine
re-install I hadn't run engine-cleanup, and then when I restored my DB
I used the "restore.sh -u postgres -f /root/ovirt.sql" instead of
doing a manual db restore which between the two of them got rid of the
issue. I'm assuming it was the engine-cleanup that sorted out the db
renaming problem though.
Once that was done I then managed to upgrade to 3.3 and I'll now do
the 3.4 upgrade.
Thanks very much for those who assisted.
Regards.
Neil Wilson.
On Thu, May 22, 2014 at 6:12 AM, Neil wrote:
> Hi guys, sorry to repost but getting a bit desperate. Is anyone able to
> assist?
>
> Thanks.
>
> Regards.
>
> Neil Wilson
>
> On 21 May 2014 12:06 PM, "Neil" wrote:
>>
>> Hi guys,
>>
>> Just a little more info on the problem. I've upgraded another oVirt
>> system before from Dreyou and it worked perfectly, however on this
>> particular system, we had to restore from backups (DB PKI and
>> etc/ovirt-engine) as the physical machine died that was hosting the
>> engine, so perhaps this is the reason we encountering this problem
>> this time around...
>>
>> Any help is greatly appreciated.
>>
>> Thank you.
>>
>> Regards.
>>
>> Neil Wilson.
>>
>>
>>
>> On Wed, May 21, 2014 at 11:46 AM, Sven Kieske
>> wrote:
>> > Hi,
>> >
>> > I don't know the exact resolution for this, but I'll add some people
>> > who managed to make it work, following this tutorial:
>> > http://wiki.dreyou.org/dokuwiki/doku.php?id=ovirt_rpm_start33
>> >
>> > See this thread on the users ML:
>> >
>> > http://lists.ovirt.org/pipermail/users/2013-December/018341.html
>> >
>> > HTH
>> >
>> >
>> > Am 20.05.2014 17:00, schrieb Neil:
>> >> Hi guys,
>> >>
>> >> I'm trying to upgrade from Dreyou to the official repo, I've installed
>> >> the official 3.2 repo (I'll do the 3.3 update once this works). I've
>> >> updated to ovirt-engine-setup.noarch 0:3.2.3-1.el6 and when I run
>> >> engine upgrade it bombs out when trying to rename my database with the
>> >> following error...
>> >>
>> >> [root@engine01 /]# cat
>> >> /var/log/ovirt-engine/ovirt-engine-upgrade_2014_05_20_16_34_21.log
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing
>> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB host value
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing
>> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB port value
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing
>> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB user value
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::332::root:: YUM: VERB:
>> >> Loaded plugins: refresh-packagekit, versionlock
>> >> 2014-05-20 16:34:21::INFO::engine-upgrade::969::root:: Info:
>> >> /etc/ovirt-engine/.pgpass file found. Continue.
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing
>> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB admin value
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing
>> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB host value
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::804::root:: found existing
>> >> pgpass file /etc/ovirt-engine/.pgpass, fetching DB port value
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::481::root:: running sql
>> >> query 'SELECT pg_database_size('engine')' on db server: 'localhost'.
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::434::root:: Executing
>> >> command --> '/usr/bin/psql -h localhost -p 5432 -U postgres -d
>> >> postgres -c SELECT pg_database_size('engine')'
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::472::root:: output =
>> >> pg_database_size
>> >> --
>> >> 11976708
>> >> (1 row)
>> >>
>> >>
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::473::root:: stderr =
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::474::root:: retcode = 0
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::1567::root:: Found mount
>> >> point of '/var/cache/yum' at '/'
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::663::root:: Checking
>> >> available space on /var/cache/yum
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::668::root:: Available space
>> >> on /var/cache/yum is 172329
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::1567::root:: Found mount
>> >> point of '/var/lib/ovirt-engine/backups' at '/'
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::663::root:: Checking
>> >> available space on /var/lib/ovirt-engine/backups
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::668::root:: Available space
>> >> on /var/lib/ovirt-engine/backups is 172329
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::1567::root:: Found mount
>> >> point of '/usr/share' at '/'
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::663::root:: Checking
>> >> available space on /usr/share
>> >> 2014-05-20 16:34:21::DEBUG::common_utils::668::root:: Available space
>> >> on /usr/share is 172329
>> >> 2014
