On Thu, Nov 12, 2015 at 4:26 PM, David Marzal Canovas <dmc(a)asambleamurcia.es
wrote:
Hi Sandro, thanks for the tips.
After a few problems, I think everything is working OK.
I already had an image of my server so I tried the path that you suggested
and this is what I found:
yum install
http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
fedup --network 22 --product=server
This show a warning but the upgrade is successful :
WARNING: potential problems with upgrade
ovirt-engine-backend-3.5.4.2-1.fc20.noarch (no replacement) requires
vdsm-jsonrpc-java-1.0.15-1.fc20.noarch (replaced by
vdsm-jsonrpc-java-1.1.5-1.fc22.noarch)
ovirt-engine-3.5.4.2-1.fc20.noarch (no replacement) requires
1:java-1.7.0-openjdk-1.7.0.79-2.5.5.0.fc20.x86_64 (replaced by
1:java-1.8.0-openjdk-1.8.0.65-3.b17.fc22.x86_64)
Continue with the upgrade at your own risk.
After reboot the system is upgraded but perl is broken due to some
packages not being up to date. This can be fixed with (after allowing dnf
in the firewall )
dnf distro-sync --setopt=deltarpm=0
Upgrade the DB and change the configuration (ovirt 3.6 needs lc_messages =
'en_US.UTF-8' )
postgresql-setup --upgrade
vim /var/lib/pgsql/data/postgresql.conf
/var/lib/pgsql/data/pg_hba.conf
Check the rest of configuration files
rpmconf -a
Then check the services because nfs has some bug and dies on startup
https://bugzilla.redhat.com/show_bug.cgi?id=1192501
https://bugzilla.redhat.com/show_bug.cgi?id=1178720
systemctl status postgresql.service nfs
until you execute
systemctl enable nfs-server.service
And now we finally can upgrade oVirt
engine-setup
It will show a warning about versionlock:
DNF Failed loading plugin: versionlock
But it would upgrade oVirt correctly.
Great!
At my first attempt I don't have any problem with the
fedup --network 22 --product=server
but I didn't modify all the necessary files and fix the nfs so at one pont
y restore the image of the server and start over.
In the second attempt (the next day) the command complaint about
ovirt-release35-006-1
Downloading failed: El paquete ovirt-release35-006-1.noarch.rpm no está
firmado (is not signed)
we add an issue with the tool we use for signing the rpms, it should be
fixed now.
I had to remove this package and the files on /etc/yum.repos.d to be
able
to upgrade Fedora to 22
yum remove ovirt-release35
rm /etc/yum.repos.d/ovirt-3.5*
I also test before trying to use fedup to just yum upgrade the system but
end with the same error so finally I delete ovirt-release35 and could
continue with the process described.
I hope this is useful if someone needs to upgrade their systems.
And thanks for an incredible product. :)
PD: Sorry for the (lack of) formating
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at
redhat.com