Hi Eli The following is the error we're getting when upgrading upstream 3.1 to 3.2: 2013-06-25 14:52:11::DEBUG::common_utils::434::root:: Executing command --> '/usr/share/ovirt-engine/dbscripts/upgrade.sh -s localhost -p 5432 -u engine -d engine_2013_06_25_14_49_31' 2013-06-25 14:52:16::DEBUG::common_utils::472::root:: output = /usr/share/ovirt-engine/dbscripts /usr/share/ovirt-engine/dbscripts upgrade script detected a change in Config, View or Stored Procedure... 2013-06-25 14:52:16::DEBUG::common_utils::473::root:: stderr = psql:drop_old_uuid_functions.sql:25: ERROR: cannot drop function uuid_nil() because extension uuid-ossp requires it HINT: You can drop extension uuid-ossp instead. CONTEXT: SQL statement "drop function if exists uuid_nil()" PL/pgSQL function __temp_drop_old_uuid_functions() line 10 at SQL statement psql:create_functions.sql:671: ERROR: must be owner of function uuid_generate_v1 Any idea how can we fix it manually? Thanks, Alex. On Tue, Jun 25, 2013 at 3:58 PM, Karli Sjöberg <Karli.Sjoberg@slu.se> wrote:
tis 2013-06-25 klockan 14:59 +0300 skrev Moran Goldboim: On 06/25/2013 02:52 PM, Alex Lourie wrote:
On Tue, Jun 25, 2013 at 1:31 PM, Karli Sjöberg
wrote:
mån 2013-06-24 klockan 12:35 +0003 skrev Alex Lourie:
On Mon, Jun 24, 2013 at 2:09 PM, Karli Sjöberg <Karli.Sjoberg@slu.se> wrote:
mån 2013-06-24 klockan 10:54 +0003 skrev Alex Lourie: > On Mon, Jun 24, 2013 at 1:26 PM, Karli Sjöberg >> <Karli.Sjoberg@slu.se> >> wrote: > > sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi Karli > >> >> >> I've written up all we know at [1], please try to follow it (if >> you >> >> haven't yet) and let us know how it goes. If anything goes wrong, >> we >> >> will look for the ways to resolve it. > >> >> > >> > Hi Alex! > > >> > Awesome job, I´m going to test this right away and let you know >> how >> > it goes. Wish me luck;) > > >> >> Good luck! May the force be with you. > > > No no, the source Alex, the source:) > /K
Sure, that one too.
Hi Karli
Well, it wasn´t with me for long, I have hit BZ 911939 and
901786,
where fedup fails to find my LVM volumes. In the dracut shell (to where it gets dropped), I have good output from blkid and lvm pvs|vgs|lvs but no nodes created in /dev/mapper and so the system cannot boot and upgrade fails. Do you have any suggestions there
might help? In the mean time, I´ll try upgrading using http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum instead, see if that gives better success.
Sorry to hear that. Different people have experienced multiple problems upgrading lvm-based F17 systems to F18. I don't think
<Karli.Sjoberg@slu.se> that that
there's a magic solution that would just work, each case is usually solved on its own.
Let us know how you progress with upgrading with yum.
Alex.
i used same article [1] and had a successful go with it - good luck...
[1] https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fed...
--
Med Vänliga Hälsningar
-------------------------------------------------------------------------------
Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg@slu.se
Yes, I had much better success following that article, and managed to upgrade fedora to 18, had to tune my kernel parameters a little for the postgres upgrade to work, but then engine-upgrade fails just as it did the last time we tried. The log is attached. Hoping to hear back from you soon with ideas on what to try next.
--
Med Vänliga Hälsningar ------------------------------------------------------------------------------- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg@slu.se