On Tue, Jun 25, 2013 at 2:58 PM, Karli Sjöberg wrote: > ** > > > 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. > > > But now the error seems different from the original one in March (if I remember correctly the original post). Could it be somehow related with this rhev one bug: https://bugzilla.redhat.com/show_bug.cgi?id=923614 and that changing permissions for the impacted objects in db before running upgrade could help?
BTW: is your environment directly created in 3.1 or did it come from a further upgrade? HIH, Gianluca
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
