4:14 a.m.
--=_35f37747b7409088194fea6f348517b4
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Hi would like to be sure of the correct upgrate path to take.
Should I first upgrade Fedora 20 -> Fedora 21 -> Fedora 22
and then upgrade oVirt from 3.5 to 3.6?
Or would be better to upgrade in the Fedora 20: oVirt 3.5 -> oVirt 3.6
and then make the OS upgrades FD20->FD21->FD22
In the release notes
http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_pre...
[1]
don't says anything about the upgrade path of the OS, but searching I'm
aware that
oVirt 3.5 is only compatible with FD20 not with 21, or 22
oVirt 3.6 is only compatible with FD20 not with 21 or 20
Thanks in advance
--
David Marzal Cánovas
Servicio de Mecanización e Informática
Asamblea Regional de Murcia
Paseo Alfonso XIII, nº53
30203 - Cartagena
Tlfno: 968326800
Links:
------
[1]
http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_pre...
--=_35f37747b7409088194fea6f348517b4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt'>
<p>Hi would like to be sure of the correct upgrate path to take.</p>
<p>Should I first upgrade Fedora 20 -> Fedora 21 -> Fedora
22</p>
<p>and then upgrade oVirt from 3.5 to 3.6?</p>
<p>Or would be better to upgrade in the Fedora 20: oVirt 3.5 -> oVirt 3=
=2E6</p>
<p>and then make the OS upgrades FD20->FD21->FD22</p>
<p>In the release notes <a
href=3D"http://www.ovirt.org/OVirt_3.6_Release_N=
otes#Install_.2F_Upgrade_from_previous_versions">http://www.ovirt...
_3.6_Release_Notes#Install_.2F_Upgrade_from_previous_versions</a></p>
<p>don't says anything about the upgrade path of the OS, but searching I'm
=
aware that</p>
<p>oVirt 3.5 is only compatible with FD20 not with 21, or 22</p>
<p>oVirt 3.6 is only compatible with FD20 not with 21 or 20</p>
<p>Thanks in advance</p>
<div>-- <br />
<table border=3D"0" cellspacing=3D"0"
cellpadding=3D"0">
<tbody>
<tr>
<td><img
src=3D"http://www.asambleamurcia.es/templates/sumandoesfuerzos/ima=
ges/ARM.png" alt=3D"" width=3D"130" height=3D"79"
/></td>
<td>David Marzal Cánovas <br />Servicio de
Mecanización =
e Informática<br />Asamblea Regional de Murcia<br />Paseo Alfonso
XI=
II, nº53<br />30203 - Cartagena<br />Tlfno: 968326800</td>
</tr>
</tbody>
</table>
</div>
</body></html>
--=_35f37747b7409088194fea6f348517b4--
1:10 a.m.
On Mon, Nov 9, 2015 at 11:14 AM, David Marzal Canovas <dmc(a)asambleamurcia.es
wrote:
Hi would like to be sure of the correct upgrate path to take.
Should I first upgrade Fedora 20 -> Fedora 21 -> Fedora 22
and then upgrade oVirt from 3.5 to 3.6?
Or would be better to upgrade in the Fedora 20: oVirt 3.5 -> oVirt 3.6
and then make the OS upgrades FD20->FD21->FD22
In the release notes
http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_pre...
don't says anything about the upgrade path of the OS, but searching I'm
aware that
oVirt 3.5 is only compatible with FD20 not with 21, or 22
oVirt 3.6 is only compatible with FD20 not with 21 or 20
Thanks in advance
Hi, upgrade from FC20 to FC22 has not been tested and you're welcome to
help testing it.
What I would suggest is:
- make an image of your existing engine (I suggest clonezilla for doing it)
- install ovirt-release36 from
http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
- fedup from fc20 to fc22 directly, without the fc21 step
- run rpmconf -a and update relevant config files (be sure to not just
overwrite them!)
- run postgresql-setup --upgrade
- run engine-setup
I suggest to update to fc22 directly because there aren't FC21 builds of
ovirt engine and the fedup process may not work as expected with missing
repos.
If the upgrade fails, you can restore the disk image created with
clonezilla and retry with a different procedure.
If you hit any issue or if you succeed let us know!
--
David Marzal Cánovas
Servicio de Mecanización e Informática
Asamblea Regional de Murcia
Paseo Alfonso XIII, nº53
30203 - Cartagena
Tlfno: 968326800
_______________________________________________
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
3:06 a.m.
I've updgraded this way: fc20->fc21->fc22, because fedup couldn't find
GPG-Key for FC22 repos.
Next step: postgresql-setup --upgrade, because postgresql refused to
start with unupgraded DB.
After this I installed oVirt 3.6 release packege and did dnf update
--best --allowerasing: it resulted in deletion of old engine packages,
but since I've got AIO install, I checked that allinone plugin had also
upgraded.
First try to run engine-setup said, that it could not connect to DB, so
I've copied old pg_hba.conf and also changed max_connections to 150 in
postgresql.conf.
After all this I've managed to successfully run engine-setup.
Hi would like to be sure of the correct upgrate path to take.
Should I first upgrade Fedora 20 -> Fedora 21 -> Fedora 22
and then upgrade oVirt from 3.5 to 3.6?
Or would be better to upgrade in the Fedora 20: oVirt 3.5 -> oVirt 3.6
and then make the OS upgrades FD20->FD21->FD22
In the release notes
http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_pre...
[1]
don't says anything about the upgrade path of the OS, but searching I'm
aware that
oVirt 3.5 is only compatible with FD20 not with 21, or 22
oVirt 3.6 is only compatible with FD20 not with 21 or 20
Thanks in advance
--
David Marzal Cánovas
Servicio de Mecanización e Informática
Asamblea Regional de Murcia
Paseo Alfonso XIII, nº53
30203 - Cartagena
Tlfno: 968326800
Links:
------
[1]
http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_pre...
2:22 p.m.
On 11/10/2015 1:10 AM, Sandro Bonazzola wrote:
Hi, upgrade from FC20 to FC22 has not been tested and you're
welcome
to help testing it.
What I would suggest is:
- make an image of your existing engine (I suggest clonezilla for
doing it)
- install ovirt-release36 from
http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
- fedup from fc20 to fc22 directly, without the fc21 step
- run rpmconf -a and update relevant config files (be sure to not just
overwrite them!)
- run postgresql-setup --upgrade
- run engine-setup
I suggest to update to fc22 directly because there aren't FC21 builds
of ovirt engine and the fedup process may not work as expected with
missing repos.
If the upgrade fails, you can restore the disk image created with
clonezilla and retry with a different procedure.
If you hit any issue or if you succeed let us know!
So I did a fedup from 20 to 22, which went fairly well. I did have some
issues though:
named was missing some libraries after the upgrade. Removing named and
reinstalling has fixed that up.
rpmconf -a is giving me the following error:
# rpmconf -a
/usr/libexec/pk-command-not-found: error while loading shared libraries:
libpackagekit-glib2.so.16: cannot open shared object file: No such file
or directory
dnf provides "*/libpackagekit-glib2.so.16"
Last metadata expiration check performed 0:59:14 ago on Sat Dec 26
13:19:20 2015.
Error: No Matches found
So not sure what's going on there. I do have PackageKit-glib-devel
installed.
postgresql-setup upgrade
Cannot upgrade because the database in /var/lib/pgsql/data is not of
compatible previous version 9.2.
What do I do about this?
I did engine-setup afterwards and everything seems to be running fine.
I did have to set my host CPU type back to Sandybridge as it wasn't
recognizing my I7 4790K. Seems to be a known issue.
I also have explanation points next to all my VMs stating that my time
zone configuration differs between the VM config and the guest config,
which they do not.
3:44 p.m.
On Sat, Dec 26, 2015 at 2:22 PM, Blaster <Blaster(a)556nato.com> wrote:
On 11/10/2015 1:10 AM, Sandro Bonazzola wrote:
>
> Hi, upgrade from FC20 to FC22 has not been tested and you're welcome to
> help testing it.
> What I would suggest is:
> - make an image of your existing engine (I suggest clonezilla for doing
> it)
> - install ovirt-release36 from
> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
> - fedup from fc20 to fc22 directly, without the fc21 step
> - run rpmconf -a and update relevant config files (be sure to not just
> overwrite them!)
> - run postgresql-setup --upgrade
> - run engine-setup
>
> I suggest to update to fc22 directly because there aren't FC21 builds of
> ovirt engine and the fedup process may not work as expected with missing
> repos.
>
> If the upgrade fails, you can restore the disk image created with
> clonezilla and retry with a different procedure.
>
> If you hit any issue or if you succeed let us know!
So I did a fedup from 20 to 22, which went fairly well. I did have some
issues though:
named was missing some libraries after the upgrade. Removing named and
reinstalling has fixed that up.
rpmconf -a is giving me the following error:
# rpmconf -a
/usr/libexec/pk-command-not-found: error while loading shared libraries:
libpackagekit-glib2.so.16: cannot open shared object file: No such file or
directory
dnf provides "*/libpackagekit-glib2.so.16"
Last metadata expiration check performed 0:59:14 ago on Sat Dec 26 13:19:20
2015.
Error: No Matches found
So not sure what's going on there. I do have PackageKit-glib-devel
installed.
Try doing "dnf reinstall *PackageKit*" to get everything correctly loaded.
postgresql-setup upgrade
Cannot upgrade because the database in /var/lib/pgsql/data is not of
compatible previous version 9.2.
What do I do about this?
The Fedora PostgreSQL packages only include the version of pgsql plus
the previous. Fedora 22 had PostgreSQL 9.4 (with upgrade capability
from 9.3, which was in Fedora 21). The way to solve that would be to
forcibly install the postgresql-upgrade package from Fedora 21 to
upgrade it correctly. I'm not sure that would work like you'd hope,
though.
I did engine-setup afterwards and everything seems to be running
fine.
Then don't worry about it, for now.
I did have to set my host CPU type back to Sandybridge as it
wasn't
recognizing my I7 4790K. Seems to be a known issue.
I also have explanation points next to all my VMs stating that my time zone
configuration differs between the VM config and the guest config, which they
do not.
Not sure why that's happening.
--
真実はいつも一つ！/ Always, there's only one truth!
11:04 a.m.
On 12/26/2015 2:22 PM, Blaster wrote:
On 11/10/2015 1:10 AM, Sandro Bonazzola wrote:
> Hi, upgrade from FC20 to FC22 has not been tested and you're welcome
> to help testing it.
> What I would suggest is:
> - make an image of your existing engine (I suggest clonezilla for
> doing it)
> - install ovirt-release36 from
> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
> - fedup from fc20 to fc22 directly, without the fc21 step
> - run rpmconf -a and update relevant config files (be sure to not
> just overwrite them!)
> - run postgresql-setup --upgrade
> - run engine-setup
>
> I suggest to update to fc22 directly because there aren't FC21 builds
> of ovirt engine and the fedup process may not work as expected with
> missing repos.
>
> If the upgrade fails, you can restore the disk image created with
> clonezilla and retry with a different procedure.
>
> If you hit any issue or if you succeed let us know!
So I did a fedup from 20 to 22, which went fairly well. I did have
some issues though:
named was missing some libraries after the upgrade. Removing named
and reinstalling has fixed that up.
rpmconf -a is giving me the following error:
# rpmconf -a
/usr/libexec/pk-command-not-found: error while loading shared
libraries: libpackagekit-glib2.so.16: cannot open shared object file:
No such file or directory
dnf provides "*/libpackagekit-glib2.so.16"
Last metadata expiration check performed 0:59:14 ago on Sat Dec 26
13:19:20 2015.
Error: No Matches found
So not sure what's going on there. I do have PackageKit-glib-devel
installed.
postgresql-setup upgrade
Cannot upgrade because the database in /var/lib/pgsql/data is not of
compatible previous version 9.2.
What do I do about this?
I did engine-setup afterwards and everything seems to be running fine.
I did have to set my host CPU type back to Sandybridge as it wasn't
recognizing my I7 4790K. Seems to be a known issue.
I also have explanation points next to all my VMs stating that my time
zone configuration differs between the VM config and the guest config,
which they do not.
Finally having a chance to get back at this. This ended up not going
anywhere near as well as I had originally thought.
The reason why the Postgress upgrade was failing was because I was still
running 9.3 for some reason after the fedup upgrade. As I started
diagnosing the known NFS server problem, I discovered after the fed22
update, it apparently only updates you to the base Fedora 22 packages.
You then need to do a dnf update to get the latest. Which then fixed my
NFS problem, but then vdsm refused to connect to the database. It was
at that point I discovered my installed version of Postgress was now @
9.4, instead of 9.3. Not sure how I got to 9.3, as I thought Fedora 20,
which is where I came from has 9.2, and Fedora 22 had 9.4.
So now I did the Postgress upgrade, which worked as expected above. But
vdsm still would not connect to the database. After googling that
issue, the only suggestion I saw was to remove the password from the
vdsm conf file and re-run engine setup. That really upset Ovirt and it
wiped out everything and proceeded to start with a fresh configuration,
wiping out my datacenter.
I do run a nightly ovirt backup, which I attempted to restore from, but
it wouldn't let me do that as my backup which was from the previous
night was for 3.5, and I was now at 3.6.1. So much for backups.
It was at that point I just decided to investigate Hosted Engine, seeing
as I was needing to start from scratch. After spending several hours
researching that, it appears HE is know where near ready for any sort of
daily driver. The WIKI how to seemed severely out of date and I
couldn't find a usable engine appliance ISO that seemed to be ready to
with out hours or days of additional hacking.
So in the end I just re-ran the All-In-One setup and spent a couple
hours rebuilding my datacenter.
So to the above steps, a dnf update needs to added as a step after the
fedup reboot.
3029
days inactive
3085
days old
5 comments
5 participants
participants (5)
-
Blaster -
David Marzal Canovas -
Neal Gompa -
Sandro Bonazzola -
Сергей Скурлаев