8:42 a.m.
Hi guys,
I'm running an older version of ovirt-engine on Centos 6.2 and I'd
like to upgrade ovirt-engine and the other corresponding packages
ovirt-engine-webadmin-portal-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-dbscripts-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-tools-common-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-backend-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-log-collector-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-iso-uploader-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-cli-3.1.0.1-1alpha.el6.noarch
ovirt-engine-jbossas-1.2-2.fc16.x86_64
ovirt-engine-restapi-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-jboss-deps-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-config-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-image-uploader-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
ovirt-engine-userportal-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-notification-service-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-genericapi-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-setup-3.1.0_0001-1.8.el6.x86_64
Using yum even if I do a yum update ovirt-engine* the only updates I get are...
ovirt-engine-cli noarch
3.1.0.6-1.el6 ovirt31-dre
144 k
ovirt-engine-sdk noarch
3.1.0.4-1.el6 ovirt31-dre
222 k
and yet I can see there are newer ovirt-engine packages available than
the ones I'm running, I've checked that the repo is enabled...
[ovirt-dre]
name=oVirt engine repo
baseurl=http://www.dreyou.org/ovirt/ovirt-engine/
http://www1.dreyou.org/ovirt/ovirt-engine/
enabled=1
gpgcheck=0
[ovirt31-dre]
name=oVirt 3.1 engine repo
baseurl=http://www.dreyou.org/ovirt/ovirt-engine31/
http://www1.dreyou.org/ovirt/ovirt-engine31/
enabled=1
gpgcheck=0
...and browsing the repo manually through a browser I see the
following packages under ovirt-engine31/
ovirt-engine-3.1.0-3.11.el6.noarch.rpm
ovirt-engine-3.1.0-3.11.el6.src.rpm
and under the ovirt-engine/ directory I see the following versions...
ovirt-engine-3.1.0-3.15.el6.noarch.rpm
ovirt-engine-3.1.0-3.15.el6.src.rpm
Anyone have any ideas why yum won't find the newer versions?
Thank you.
Regards.
Neil.
1:04 p.m.
On 07/31/2012 09:42 AM, Neil wrote:
Hi guys,
I'm running an older version of ovirt-engine on Centos 6.2 and I'd
like to upgrade ovirt-engine and the other corresponding packages
ovirt-engine-webadmin-portal-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-dbscripts-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-tools-common-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-backend-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-log-collector-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-iso-uploader-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-cli-3.1.0.1-1alpha.el6.noarch
ovirt-engine-jbossas-1.2-2.fc16.x86_64
ovirt-engine-restapi-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-jboss-deps-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-config-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-image-uploader-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
ovirt-engine-userportal-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-notification-service-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-genericapi-3.1.0_0001-1.8.el6.x86_64
ovirt-engine-setup-3.1.0_0001-1.8.el6.x86_64
Using yum even if I do a yum update ovirt-engine* the only updates I get are...
ovirt-engine-cli noarch
3.1.0.6-1.el6 ovirt31-dre
144 k
ovirt-engine-sdk noarch
3.1.0.4-1.el6 ovirt31-dre
222 k
and yet I can see there are newer ovirt-engine packages available than
the ones I'm running, I've checked that the repo is enabled...
[ovirt-dre]
name=oVirt engine repo
baseurl=http://www.dreyou.org/ovirt/ovirt-engine/
http://www1.dreyou.org/ovirt/ovirt-engine/
enabled=1
gpgcheck=0
[ovirt31-dre]
name=oVirt 3.1 engine repo
baseurl=http://www.dreyou.org/ovirt/ovirt-engine31/
http://www1.dreyou.org/ovirt/ovirt-engine31/
enabled=1
gpgcheck=0
...and browsing the repo manually through a browser I see the
following packages under ovirt-engine31/
ovirt-engine-3.1.0-3.11.el6.noarch.rpm
ovirt-engine-3.1.0-3.11.el6.src.rpm
and under the ovirt-engine/ directory I see the following versions...
ovirt-engine-3.1.0-3.15.el6.noarch.rpm
ovirt-engine-3.1.0-3.15.el6.src.rpm
Anyone have any ideas why yum won't find the newer versions?
Thank you.
Regards.
Neil.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
you need to run the upgrade script since the setup locks the rpm's to
make sure the code isn't updated without updating the db in sync
1:55 p.m.
----- Original Message -----
On 07/31/2012 09:42 AM, Neil wrote:
> Hi guys,
>
> I'm running an older version of ovirt-engine on Centos 6.2 and I'd
> like to upgrade ovirt-engine and the other corresponding packages
>
> ovirt-engine-webadmin-portal-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-dbscripts-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-tools-common-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-backend-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-log-collector-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-iso-uploader-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-cli-3.1.0.1-1alpha.el6.noarch
> ovirt-engine-jbossas-1.2-2.fc16.x86_64
> ovirt-engine-restapi-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-jboss-deps-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-config-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-image-uploader-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
> ovirt-engine-userportal-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-notification-service-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-genericapi-3.1.0_0001-1.8.el6.x86_64
> ovirt-engine-setup-3.1.0_0001-1.8.el6.x86_64
>
> Using yum even if I do a yum update ovirt-engine* the only updates
> I get are...
>
> ovirt-engine-cli noarch
> 3.1.0.6-1.el6 ovirt31-dre
> 144 k
> ovirt-engine-sdk noarch
> 3.1.0.4-1.el6 ovirt31-dre
> 222 k
>
> and yet I can see there are newer ovirt-engine packages available
> than
> the ones I'm running, I've checked that the repo is enabled...
>
> [ovirt-dre]
> name=oVirt engine repo
> baseurl=http://www.dreyou.org/ovirt/ovirt-engine/
> http://www1.dreyou.org/ovirt/ovirt-engine/
> enabled=1
> gpgcheck=0
>
> [ovirt31-dre]
> name=oVirt 3.1 engine repo
> baseurl=http://www.dreyou.org/ovirt/ovirt-engine31/
> http://www1.dreyou.org/ovirt/ovirt-engine31/
> enabled=1
> gpgcheck=0
>
> ...and browsing the repo manually through a browser I see the
> following packages under ovirt-engine31/
>
> ovirt-engine-3.1.0-3.11.el6.noarch.rpm
> ovirt-engine-3.1.0-3.11.el6.src.rpm
>
> and under the ovirt-engine/ directory I see the following
> versions...
>
> ovirt-engine-3.1.0-3.15.el6.noarch.rpm
> ovirt-engine-3.1.0-3.15.el6.src.rpm
>
> Anyone have any ideas why yum won't find the newer versions?
>
> Thank you.
>
> Regards.
>
> Neil.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
you need to run the upgrade script since the setup locks the rpm's to
make sure the code isn't updated without updating the db in sync
we're using yum versionlock in order to prevent unintended upgrades.
just run engine-upgrade.
5:31 p.m.
On Tue, Jul 31, 2012 at 1:55 PM, Ofer Schreiber <oschreib(a)redhat.com> wrote:
> you need to run the upgrade script since the setup locks the
rpm's to
> make sure the code isn't updated without updating the db in sync
we're using yum versionlock in order to prevent unintended upgrades.
just run engine-upgrade.
Hi again,
When running engine-upgrade I received the following message...
12 Updates available:
* ovirt-engine-3.1.0-3.15.el6.noarch
* ovirt-engine-backend-3.1.0-3.15.el6.noarch
* ovirt-engine-config-3.1.0-3.15.el6.noarch
* ovirt-engine-dbscripts-3.1.0-3.15.el6.noarch
* ovirt-engine-genericapi-3.1.0-3.15.el6.noarch
* ovirt-engine-notification-service-3.1.0-3.15.el6.noarch
* ovirt-engine-restapi-3.1.0-3.15.el6.noarch
* ovirt-engine-setup-3.1.0-3.15.el6.noarch
* ovirt-engine-tools-common-3.1.0-3.15.el6.noarch
* ovirt-engine-userportal-3.1.0-3.15.el6.noarch
* ovirt-engine-webadmin-portal-3.1.0-3.15.el6.noarch
* vdsm-bootstrap-4.10.0-0.191.9.el6.noarch
Error: New ovirt-engine-setup rpm available via yum.
Please execute `yum update ovirt-engine-setup`, then re-execute
'engine-upgrade'.
To use the current ovirt-engine-setup rpm, execute 'engine-upgrade
--force-current-setup-rpm'.
...I tried running yum update ovirt-engine-setup as it said, but this
finds no package to upgrade, should I try running the 'engine-upgrade
--force-current-setup-rpm' or is there something else I should rather
do?
Any thoughts on this?
Thanks again.
Regards.
Neil Wilson.
5:48 p.m.
can you please attach the log file? (/var/log/ovirt-engine/engine-upgrade-DATE.log)
----- Original Message -----
On Tue, Jul 31, 2012 at 1:55 PM, Ofer Schreiber
<oschreib(a)redhat.com>
wrote:
>> you need to run the upgrade script since the setup locks the rpm's
>> to
>> make sure the code isn't updated without updating the db in sync
>
> we're using yum versionlock in order to prevent unintended
> upgrades.
> just run engine-upgrade.
>
Hi again,
When running engine-upgrade I received the following message...
12 Updates available:
* ovirt-engine-3.1.0-3.15.el6.noarch
* ovirt-engine-backend-3.1.0-3.15.el6.noarch
* ovirt-engine-config-3.1.0-3.15.el6.noarch
* ovirt-engine-dbscripts-3.1.0-3.15.el6.noarch
* ovirt-engine-genericapi-3.1.0-3.15.el6.noarch
* ovirt-engine-notification-service-3.1.0-3.15.el6.noarch
* ovirt-engine-restapi-3.1.0-3.15.el6.noarch
* ovirt-engine-setup-3.1.0-3.15.el6.noarch
* ovirt-engine-tools-common-3.1.0-3.15.el6.noarch
* ovirt-engine-userportal-3.1.0-3.15.el6.noarch
* ovirt-engine-webadmin-portal-3.1.0-3.15.el6.noarch
* vdsm-bootstrap-4.10.0-0.191.9.el6.noarch
Error: New ovirt-engine-setup rpm available via yum.
Please execute `yum update ovirt-engine-setup`, then re-execute
'engine-upgrade'.
To use the current ovirt-engine-setup rpm, execute 'engine-upgrade
--force-current-setup-rpm'.
...I tried running yum update ovirt-engine-setup as it said, but this
finds no package to upgrade, should I try running the 'engine-upgrade
--force-current-setup-rpm' or is there something else I should rather
do?
Any thoughts on this?
Thanks again.
Regards.
Neil Wilson.
9:30 a.m.
Hi all,
Thanks for coming back to me Ofer.
On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber <oschreib(a)redhat.com> wrote:
can you please attach the log file?
(/var/log/ovirt-engine/engine-upgrade-DATE.log)
Attached is the log as requested.
Much appreciated.
Regards.
Neil Wilson.
5:17 p.m.
----- Original Message -----
Hi all,
Thanks for coming back to me Ofer.
On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber <oschreib(a)redhat.com>
wrote:
> can you please attach the log file?
> (/var/log/ovirt-engine/engine-upgrade-DATE.log)
Attached is the log as requested.
it seems that you're using a very old 3.1 build, which we never released during the
beta process (afair).
this build is a x86_64 build, which confuses the upgrade script (since new rpms are
noarch).
I can't guarantee it will work fine (although I can't think of any reason it
won't), but using the --force-setup... parameter is a good option.
Actually, we already fixed this bug upstream, but I'm not sure it will get into 3.1.
Much appreciated.
Regards.
Neil Wilson.
7:29 p.m.
On Wed, Aug 1, 2012 at 10:17 AM, Ofer Schreiber <oschreib(a)redhat.com> wrote:
----- Original Message -----
> Hi all,
>
> Thanks for coming back to me Ofer.
>
> On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber <oschreib(a)redhat.com>
> wrote:
> > can you please attach the log file?
> > (/var/log/ovirt-engine/engine-upgrade-DATE.log)
>
> Attached is the log as requested.
it seems that you're using a very old 3.1 build, which we never released during the
beta process (afair).
this build is a x86_64 build, which confuses the upgrade script (since new rpms are
noarch).
I can't guarantee it will work fine (although I can't think of any reason it
won't), but using the --force-setup... parameter is a good option.
Actually, we already fixed this bug upstream, but I'm not sure it will get into 3.1.
>
> Much appreciated.
>
> Regards.
>
> Neil Wilson.
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
After seeing this thread I decided to attempt to reproduce the errors
and see if I could get my same version to upgrade...
This is what I have installed now,
# rpm -qa ovirt*
ovirt-engine-userportal-3.1.0_0001-1.8.el6.noarch
ovirt-engine-tools-common-3.1.0_0001-1.8.el6.noarch
ovirt-engine-genericapi-3.1.0_0001-1.8.el6.noarch
ovirt-engine-cli-3.1.0.2-1alpha.el6.noarch
ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
ovirt-log-collector-3.1.0-11alpha.el6.noarch
ovirt-engine-dbscripts-3.1.0_0001-1.8.el6.noarch
ovirt-engine-config-3.1.0_0001-1.8.el6.noarch
ovirt-engine-setup-3.1.0_0001-1.8.el6.noarch
ovirt-engine-backend-3.1.0_0001-1.8.el6.noarch
ovirt-engine-3.1.0_0001-1.8.el6.noarch
ovirt-iso-uploader-3.1.0-11alpha.el6.noarch
ovirt-image-uploader-3.1.0-11alpha.el6.noarch
ovirt-engine-jbossas711-1-0.x86_64
ovirt-engine-restapi-3.1.0_0001-1.8.el6.noarch
ovirt-engine-webadmin-portal-3.1.0_0001-1.8.el6.noarch
ovirt-engine-notification-service-3.1.0_0001-1.8.el6.noarch
However when I run engine-check-upgrade no updates are found
# engine-check-update
Loaded plugins: fastestmirror, priorities, versionlock
Checking for updates... (This may take several minutes)
Loading mirror speeds from cached hostfile
* base: centos.mirror.lstn.net
* epel: mirror.unl.edu
* extras: dallas.tx.mirror.xygenhosting.com
* updates: mirrors.liquidweb.com
No updates available
What's strange is if I disable the versionlock plugin and check
updates in yum , I only see 2 ovirt related items
# yum --disableplugin=versionlock check-update
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* base: centos.mirror.lstn.net
* epel: mirror.unl.edu
* extras: dallas.tx.mirror.xygenhosting.com
* updates: mirrors.liquidweb.com
<snip>
ovirt-engine-cli.noarch
3.1.0.6-1.el6
ovirt-dre
ovirt-engine-sdk.noarch
3.1.0.4-1.el6
ovirt-dre
<snip>
Have already done a 'yum clean all', and ensured my repo files match
those posted on the website. Any tips on how to do an upgrade?
Thanks
- Trey
9:11 p.m.
--Apple-Mail-BDE6EFD0-EBB0-45ED-8CE0-5D79784BEEFC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
Once again- you have an unsupported version of ovirt-engine.
The reason engine-upgrade doesn't work is that 3.1.0_0001-1> 3.1.0-2
On 1 Aug 2012, at 21:32, Trey Dockendorf <treydock(a)gmail.com> wrote:
On Wed, Aug 1, 2012 at 10:17 AM, Ofer Schreiber
<oschreib(a)redhat.com> wrot=
e:
>=20
>=20
> ----- Original Message -----
>> Hi all,
>>=20
>> Thanks for coming back to me Ofer.
>>=20
>> On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber <oschreib(a)redhat.com>
>> wrote:
>>> can you please attach the log file?
>>> (/var/log/ovirt-engine/engine-upgrade-DATE.log)
>>=20
>> Attached is the log as requested.
>=20
> it seems that you're using a very old 3.1 build, which we never released d=
uring the beta process (afair).
> this build is a x86_64 build, which confuses the upgrade script
(since ne=
w rpms are noarch).
>=20
> I can't guarantee it will work fine (although I can't think of any reason=
it won't), but using the --force-setup... parameter is a good option.
>=20
> Actually, we already fixed this bug upstream, but I'm not sure it will ge=
t into 3.1.
>=20
>=20
>>=20
>> Much appreciated.
>>=20
>> Regards.
>>=20
>> Neil Wilson.
>>=20
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
=20
=20
After seeing this thread I decided to attempt to reproduce the errors
and see if I could get my same version to upgrade...
=20
This is what I have installed now,
=20
# rpm -qa ovirt*
ovirt-engine-userportal-3.1.0_0001-1.8.el6.noarch
ovirt-engine-tools-common-3.1.0_0001-1.8.el6.noarch
ovirt-engine-genericapi-3.1.0_0001-1.8.el6.noarch
ovirt-engine-cli-3.1.0.2-1alpha.el6.noarch
ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
ovirt-log-collector-3.1.0-11alpha.el6.noarch
ovirt-engine-dbscripts-3.1.0_0001-1.8.el6.noarch
ovirt-engine-config-3.1.0_0001-1.8.el6.noarch
ovirt-engine-setup-3.1.0_0001-1.8.el6.noarch
ovirt-engine-backend-3.1.0_0001-1.8.el6.noarch
ovirt-engine-3.1.0_0001-1.8.el6.noarch
ovirt-iso-uploader-3.1.0-11alpha.el6.noarch
ovirt-image-uploader-3.1.0-11alpha.el6.noarch
ovirt-engine-jbossas711-1-0.x86_64
ovirt-engine-restapi-3.1.0_0001-1.8.el6.noarch
ovirt-engine-webadmin-portal-3.1.0_0001-1.8.el6.noarch
ovirt-engine-notification-service-3.1.0_0001-1.8.el6.noarch
=20
However when I run engine-check-upgrade no updates are found
=20
=20
# engine-check-update
Loaded plugins: fastestmirror, priorities, versionlock
Checking for updates... (This may take several minutes)
Loading mirror speeds from cached hostfile
* base: centos.mirror.lstn.net
* epel: mirror.unl.edu
* extras: dallas.tx.mirror.xygenhosting.com
* updates: mirrors.liquidweb.com
No updates available
=20
What's strange is if I disable the versionlock plugin and check
updates in yum , I only see 2 ovirt related items
=20
# yum --disableplugin=3Dversionlock check-update
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* base: centos.mirror.lstn.net
* epel: mirror.unl.edu
* extras: dallas.tx.mirror.xygenhosting.com
* updates: mirrors.liquidweb.com
=20
<snip>
ovirt-engine-cli.noarch
3.1.0.6-1.el6
=20
ovirt-dre
ovirt-engine-sdk.noarch
3.1.0.4-1.el6
=20
ovirt-dre
<snip>
=20
Have already done a 'yum clean all', and ensured my repo files match
those posted on the website. Any tips on how to do an upgrade?
=20
Thanks
- Trey
--Apple-Mail-BDE6EFD0-EBB0-45ED-8CE0-5D79784BEEFC
Content-Transfer-Encoding: base64
Content-Type: text/html;
charset=utf-8
PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPjxkaXY+PGRpdiBzdHls
ZT0idGV4dC1hbGlnbjogbGVmdDtkaXJlY3Rpb246IGx0cjsgIj5PbmNlIGFnYWluLSB5b3UgaGF2
ZSBhbiB1bnN1cHBvcnRlZCB2ZXJzaW9uIG9mIG92aXJ0LWVuZ2luZS48L2Rpdj48ZGl2IHN0eWxl
PSJ0ZXh0LWFsaWduOiBsZWZ0O2RpcmVjdGlvbjogbHRyOyAiPjxicj48L2Rpdj48ZGl2IHN0eWxl
PSJ0ZXh0LWFsaWduOiBsZWZ0O2RpcmVjdGlvbjogbHRyOyAiPlRoZSByZWFzb24gZW5naW5lLXVw
Z3JhZGUgZG9lc24ndCB3b3JrIGlzIHRoYXQgMy4xLjBfMDAwMS0xJmd0OyAzLjEuMC0yPC9kaXY+
PGJyPjxkaXYgc3R5bGU9ImRpcmVjdGlvbjogcnRsOyI+PGJyPjwvZGl2PjwvZGl2PjxkaXY+PGJy
Pk9uIDEgQXVnIDIwMTIsIGF0IDIxOjMyLCBUcmV5IERvY2tlbmRvcmYgJmx0OzxhIGhyZWY9Im1h
aWx0bzp0cmV5ZG9ja0BnbWFpbC5jb20iPnRyZXlkb2NrQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3Rl
Ojxicj48YnI+PC9kaXY+PGRpdj48L2Rpdj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2Pjxz
cGFuPk9uIFdlZCwgQXVnIDEsIDIwMTIgYXQgMTA6MTcgQU0sIE9mZXIgU2NocmVpYmVyICZsdDs8
YSBocmVmPSJtYWlsdG86b3NjaHJlaWJAcmVkaGF0LmNvbSI+b3NjaHJlaWJAcmVkaGF0LmNvbTwv
YT4mZ3Q7IHdyb3RlOjwvc3Bhbj48YnI+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9z
cGFuPjxicj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFu
Pjxicj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+LS0tLS0gT3Jp
Z2luYWwgTWVzc2FnZSAtLS0tLTwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjxibG9ja3F1b3RlIHR5
cGU9ImNpdGUiPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPkhpIGFsbCw8L3NwYW4+PGJy
PjwvYmxvY2txdW90ZT48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGJsb2Nr
cXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxicj48L2Jsb2NrcXVvdGU+PC9ibG9ja3F1
b3RlPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFu
PlRoYW5rcyBmb3IgY29taW5nIGJhY2sgdG8gbWUgT2Zlci48L3NwYW4+PGJyPjwvYmxvY2txdW90
ZT48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGJsb2NrcXVvdGUgdHlwZT0i
Y2l0ZSI+PHNwYW4+PC9zcGFuPjxicj48L2Jsb2NrcXVvdGU+PC9ibG9ja3F1b3RlPjxibG9ja3F1
b3RlIHR5cGU9ImNpdGUiPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPk9uIFR1ZSwgSnVs
IDMxLCAyMDEyIGF0IDU6NDggUE0sIE9mZXIgU2NocmVpYmVyICZsdDs8YSBocmVmPSJtYWlsdG86
b3NjaHJlaWJAcmVkaGF0LmNvbSI+b3NjaHJlaWJAcmVkaGF0LmNvbTwvYT4mZ3Q7PC9zcGFuPjxi
cj48L2Jsb2NrcXVvdGU+PC9ibG9ja3F1b3RlPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPndyb3RlOjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjwv
YmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48YmxvY2txdW90ZSB0eXBlPSJjaXRl
Ij48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5jYW4geW91IHBsZWFzZSBhdHRhY2ggdGhl
IGxvZyBmaWxlPzwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjwvYmxvY2txdW90ZT48L2Jsb2NrcXVv
dGU+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGJsb2Nr
cXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+KC92YXIvbG9nL292aXJ0LWVuZ2luZS9lbmdpbmUtdXBn
cmFkZS1EQVRFLmxvZyk8L3NwYW4+PGJyPjwvYmxvY2txdW90ZT48L2Jsb2NrcXVvdGU+PC9ibG9j
a3F1b3RlPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxz
cGFuPjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjwvYmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBl
PSJjaXRlIj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5BdHRhY2hlZCBpcyB0aGUgbG9n
IGFzIHJlcXVlc3RlZC48L3NwYW4+PGJyPjwvYmxvY2txdW90ZT48L2Jsb2NrcXVvdGU+PGJsb2Nr
cXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxicj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVv
dGUgdHlwZT0iY2l0ZSI+PHNwYW4+aXQgc2VlbXMgdGhhdCB5b3UncmUgdXNpbmcgYSB2ZXJ5IG9s
ZCAzLjEgYnVpbGQsIHdoaWNoIHdlIG5ldmVyIHJlbGVhc2VkIGR1cmluZyB0aGUgYmV0YSBwcm9j
ZXNzIChhZmFpcikuPC9zcGFuPjxicj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0iY2l0
ZSI+PHNwYW4+dGhpcyBidWlsZCBpcyBhIHg4Nl82NCBidWlsZCwgd2hpY2ggY29uZnVzZXMgdGhl
IHVwZ3JhZGUgc2NyaXB0IChzaW5jZSBuZXcgcnBtcyBhcmUgbm9hcmNoKS48L3NwYW4+PGJyPjwv
YmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj48L3NwYW4+PGJyPjwvYmxv
Y2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5JIGNhbid0IGd1YXJhbnRlZSBp
dCB3aWxsIHdvcmsgZmluZSAoYWx0aG91Z2ggSSBjYW4ndCB0aGluayBvZiBhbnkgcmVhc29uIGl0
IHdvbid0KSwgYnV0IHVzaW5nIHRoZSAtLWZvcmNlLXNldHVwLi4uIHBhcmFtZXRlciBpcyBhIGdv
b2Qgb3B0aW9uLjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUi
PjxzcGFuPjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxz
cGFuPkFjdHVhbGx5LCB3ZSBhbHJlYWR5IGZpeGVkIHRoaXMgYnVnIHVwc3RyZWFtLCBidXQgSSdt
IG5vdCBzdXJlIGl0IHdpbGwgZ2V0IGludG8gMy4xLjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjxi
bG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjxibG9ja3F1
b3RlIHR5cGU9ImNpdGUiPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPjwvc3Bhbj48YnI+
PC9ibG9ja3F1b3RlPjwvYmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48YmxvY2tx
dW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5NdWNoIGFwcHJlY2lhdGVkLjwvc3Bhbj48YnI+PC9ibG9j
a3F1b3RlPjwvYmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48YmxvY2txdW90ZSB0
eXBlPSJjaXRlIj48c3Bhbj48L3NwYW4+PGJyPjwvYmxvY2txdW90ZT48L2Jsb2NrcXVvdGU+PGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+UmVnYXJk
cy48L3NwYW4+PGJyPjwvYmxvY2txdW90ZT48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0i
Y2l0ZSI+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxicj48L2Jsb2NrcXVv
dGU+PC9ibG9ja3F1b3RlPjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxibG9ja3F1b3RlIHR5cGU9
ImNpdGUiPjxzcGFuPk5laWwgV2lsc29uLjwvc3Bhbj48YnI+PC9ibG9ja3F1b3RlPjwvYmxvY2tx
dW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bh
bj48L3NwYW4+PGJyPjwvYmxvY2txdW90ZT48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0i
Y2l0ZSI+PHNwYW4+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X188L3NwYW4+PGJyPjwvYmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5V
c2VycyBtYWlsaW5nIGxpc3Q8L3NwYW4+PGJyPjwvYmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBl
PSJjaXRlIj48c3Bhbj48YSBocmVmPSJtYWlsdG86VXNlcnNAb3ZpcnQub3JnIj5Vc2Vyc0Bvdmly
dC5vcmc8L2E+PC9zcGFuPjxicj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+
PHNwYW4+PGEgaHJlZj0iaHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Vz
ZXJzIj5odHRwOi8vbGlzdHMub3ZpcnQub3JnL21haWxtYW4vbGlzdGluZm8vdXNlcnM8L2E+PC9z
cGFuPjxicj48L2Jsb2NrcXVvdGU+PHNwYW4+PC9zcGFuPjxicj48c3Bhbj48L3NwYW4+PGJyPjxz
cGFuPkFmdGVyIHNlZWluZyB0aGlzIHRocmVhZCBJIGRlY2lkZWQgdG8gYXR0ZW1wdCB0byByZXBy
b2R1Y2UgdGhlIGVycm9yczwvc3Bhbj48YnI+PHNwYW4+YW5kIHNlZSBpZiBJIGNvdWxkIGdldCBt
eSBzYW1lIHZlcnNpb24gdG8gdXBncmFkZS4uLjwvc3Bhbj48YnI+PHNwYW4+PC9zcGFuPjxicj48
c3Bhbj5UaGlzIGlzIHdoYXQgSSBoYXZlIGluc3RhbGxlZCBub3csPC9zcGFuPjxicj48c3Bhbj48
L3NwYW4+PGJyPjxzcGFuPiMgcnBtIC1xYSBvdmlydCo8L3NwYW4+PGJyPjxzcGFuPm92aXJ0LWVu
Z2luZS11c2VycG9ydGFsLTMuMS4wXzAwMDEtMS44LmVsNi5ub2FyY2g8L3NwYW4+PGJyPjxzcGFu
Pm92aXJ0LWVuZ2luZS10b29scy1jb21tb24tMy4xLjBfMDAwMS0xLjguZWw2Lm5vYXJjaDwvc3Bh
bj48YnI+PHNwYW4+b3ZpcnQtZW5naW5lLWdlbmVyaWNhcGktMy4xLjBfMDAwMS0xLjguZWw2Lm5v
YXJjaDwvc3Bhbj48YnI+PHNwYW4+b3ZpcnQtZW5naW5lLWNsaS0zLjEuMC4yLTFhbHBoYS5lbDYu
bm9hcmNoPC9zcGFuPjxicj48c3Bhbj5vdmlydC1lbmdpbmUtc2RrLTMuMS4wLjEtMWFscGhhLmVs
Ni5ub2FyY2g8L3NwYW4+PGJyPjxzcGFuPm92aXJ0LWxvZy1jb2xsZWN0b3ItMy4xLjAtMTFhbHBo
YS5lbDYubm9hcmNoPC9zcGFuPjxicj48c3Bhbj5vdmlydC1lbmdpbmUtZGJzY3JpcHRzLTMuMS4w
XzAwMDEtMS44LmVsNi5ub2FyY2g8L3NwYW4+PGJyPjxzcGFuPm92aXJ0LWVuZ2luZS1jb25maWct
My4xLjBfMDAwMS0xLjguZWw2Lm5vYXJjaDwvc3Bhbj48YnI+PHNwYW4+b3ZpcnQtZW5naW5lLXNl
dHVwLTMuMS4wXzAwMDEtMS44LmVsNi5ub2FyY2g8L3NwYW4+PGJyPjxzcGFuPm92aXJ0LWVuZ2lu
ZS1iYWNrZW5kLTMuMS4wXzAwMDEtMS44LmVsNi5ub2FyY2g8L3NwYW4+PGJyPjxzcGFuPm92aXJ0
LWVuZ2luZS0zLjEuMF8wMDAxLTEuOC5lbDYubm9hcmNoPC9zcGFuPjxicj48c3Bhbj5vdmlydC1p
c28tdXBsb2FkZXItMy4xLjAtMTFhbHBoYS5lbDYubm9hcmNoPC9zcGFuPjxicj48c3Bhbj5vdmly
dC1pbWFnZS11cGxvYWRlci0zLjEuMC0xMWFscGhhLmVsNi5ub2FyY2g8L3NwYW4+PGJyPjxzcGFu
Pm92aXJ0LWVuZ2luZS1qYm9zc2FzNzExLTEtMC54ODZfNjQ8L3NwYW4+PGJyPjxzcGFuPm92aXJ0
LWVuZ2luZS1yZXN0YXBpLTMuMS4wXzAwMDEtMS44LmVsNi5ub2FyY2g8L3NwYW4+PGJyPjxzcGFu
Pm92aXJ0LWVuZ2luZS13ZWJhZG1pbi1wb3J0YWwtMy4xLjBfMDAwMS0xLjguZWw2Lm5vYXJjaDwv
c3Bhbj48YnI+PHNwYW4+b3ZpcnQtZW5naW5lLW5vdGlmaWNhdGlvbi1zZXJ2aWNlLTMuMS4wXzAw
MDEtMS44LmVsNi5ub2FyY2g8L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+SG93ZXZl
ciB3aGVuIEkgcnVuIGVuZ2luZS1jaGVjay11cGdyYWRlIG5vIHVwZGF0ZXMgYXJlIGZvdW5kPC9z
cGFuPjxicj48c3Bhbj48L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+IyBlbmdpbmUt
Y2hlY2stdXBkYXRlPC9zcGFuPjxicj48c3Bhbj5Mb2FkZWQgcGx1Z2luczogZmFzdGVzdG1pcnJv
ciwgcHJpb3JpdGllcywgdmVyc2lvbmxvY2s8L3NwYW4+PGJyPjxzcGFuPkNoZWNraW5nIGZvciB1
cGRhdGVzLi4uIChUaGlzIG1heSB0YWtlIHNldmVyYWwgbWludXRlcyk8L3NwYW4+PGJyPjxzcGFu
PkxvYWRpbmcgbWlycm9yIHNwZWVkcyBmcm9tIGNhY2hlZCBob3N0ZmlsZTwvc3Bhbj48YnI+PHNw
YW4+ICogYmFzZTogPGEgaHJlZj0iaHR0cDovL2NlbnRvcy5taXJyb3IubHN0bi5uZXQiPmNlbnRv
cy5taXJyb3IubHN0bi5uZXQ8L2E+PC9zcGFuPjxicj48c3Bhbj4gKiBlcGVsOiA8YSBocmVmPSJo
dHRwOi8vbWlycm9yLnVubC5lZHUiPm1pcnJvci51bmwuZWR1PC9hPjwvc3Bhbj48YnI+PHNwYW4+
ICogZXh0cmFzOiBkYWxsYXMudHgubWlycm9yLnh5Z2VuaG9zdGluZy5jb208L3NwYW4+PGJyPjxz
cGFuPiAqIHVwZGF0ZXM6IDxhIGhyZWY9Imh0dHA6Ly9taXJyb3JzLmxpcXVpZHdlYi5jb20iPm1p
cnJvcnMubGlxdWlkd2ViLmNvbTwvYT48L3NwYW4+PGJyPjxzcGFuPk5vIHVwZGF0ZXMgYXZhaWxh
YmxlPC9zcGFuPjxicj48c3Bhbj48L3NwYW4+PGJyPjxzcGFuPldoYXQncyBzdHJhbmdlIGlzIGlm
IEkgZGlzYWJsZSB0aGUgdmVyc2lvbmxvY2sgcGx1Z2luIGFuZCBjaGVjazwvc3Bhbj48YnI+PHNw
YW4+dXBkYXRlcyBpbiB5dW0gLCBJIG9ubHkgc2VlIDIgb3ZpcnQgcmVsYXRlZCBpdGVtczwvc3Bh
bj48YnI+PHNwYW4+PC9zcGFuPjxicj48c3Bhbj4jIHl1bSAtLWRpc2FibGVwbHVnaW49dmVyc2lv
bmxvY2sgY2hlY2stdXBkYXRlPC9zcGFuPjxicj48c3Bhbj5Mb2FkZWQgcGx1Z2luczogZmFzdGVz
dG1pcnJvciwgcHJpb3JpdGllczwvc3Bhbj48YnI+PHNwYW4+TG9hZGluZyBtaXJyb3Igc3BlZWRz
IGZyb20gY2FjaGVkIGhvc3RmaWxlPC9zcGFuPjxicj48c3Bhbj4gKiBiYXNlOiA8YSBocmVmPSJo
dHRwOi8vY2VudG9zLm1pcnJvci5sc3RuLm5ldCI+Y2VudG9zLm1pcnJvci5sc3RuLm5ldDwvYT48
L3NwYW4+PGJyPjxzcGFuPiAqIGVwZWw6IDxhIGhyZWY9Imh0dHA6Ly9taXJyb3IudW5sLmVkdSI+
bWlycm9yLnVubC5lZHU8L2E+PC9zcGFuPjxicj48c3Bhbj4gKiBleHRyYXM6IGRhbGxhcy50eC5t
aXJyb3IueHlnZW5ob3N0aW5nLmNvbTwvc3Bhbj48YnI+PHNwYW4+ICogdXBkYXRlczogPGEgaHJl
Zj0iaHR0cDovL21pcnJvcnMubGlxdWlkd2ViLmNvbSI+bWlycm9ycy5saXF1aWR3ZWIuY29tPC9h
Pjwvc3Bhbj48YnI+PHNwYW4+PC9zcGFuPjxicj48c3Bhbj4mbHQ7c25pcCZndDs8L3NwYW4+PGJy
PjxzcGFuPm92aXJ0LWVuZ2luZS1jbGkubm9hcmNoPC9zcGFuPjxicj48c3Bhbj4gJm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7My4xLjAuNi0xLmVsNjwvc3Bhbj48YnI+PHNwYW4+PC9zcGFuPjxicj48c3Bh
bj4gJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7b3ZpcnQtZHJlPC9zcGFuPjxicj48c3Bhbj5vdmlydC1lbmdp
bmUtc2RrLm5vYXJjaDwvc3Bhbj48YnI+PHNwYW4+ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzMuMS4w
LjQtMS5lbDY8L3NwYW4+PGJyPjxzcGFuPjwvc3Bhbj48YnI+PHNwYW4+ICZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwO292aXJ0LWRyZTwvc3Bhbj48YnI+PHNwYW4+Jmx0O3NuaXAmZ3Q7PC9zcGFuPjxicj48c3Bh
bj48L3NwYW4+PGJyPjxzcGFuPkhhdmUgYWxyZWFkeSBkb25lIGEgJ3l1bSBjbGVhbiBhbGwnLCBh
bmQgZW5zdXJlZCBteSByZXBvIGZpbGVzIG1hdGNoPC9zcGFuPjxicj48c3Bhbj50aG9zZSBwb3N0
ZWQgb24gdGhlIHdlYnNpdGUuICZuYnNwO0FueSB0aXBzIG9uIGhvdyB0byBkbyBhbiB1cGdyYWRl
Pzwvc3Bhbj48YnI+PHNwYW4+PC9zcGFuPjxicj48c3Bhbj5UaGFua3M8L3NwYW4+PGJyPjxzcGFu
Pi0gVHJleTwvc3Bhbj48YnI+PC9kaXY+PC9ibG9ja3F1b3RlPjwvYm9keT48L2h0bWw+
--Apple-Mail-BDE6EFD0-EBB0-45ED-8CE0-5D79784BEEFC--
9:41 p.m.
This is a multi-part message in MIME format.
--------------090101000308010305080704
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
That is actually the same as beta1. Or the same version used on testing
day. To upgrade You have to.
Yum Remove ovirt-engine vdsm
After all the packages are installed. Make sure you are using his the
3.1 repo and not the devel one that is based on master but hasn't been
updated recently.
Yum install ovirt-engine
Run the engine-upgrade and it should give you should tell you something
about the version being the same but force-upgrade the setup.
Thanks
Robert
On 08/01/2012 03:11 PM, Ofer Schreiber wrote:
Once again- you have an unsupported version of ovirt-engine.
The reason engine-upgrade doesn't work is that 3.1.0_0001-1> 3.1.0-2
On 1 Aug 2012, at 21:32, Trey Dockendorf <treydock(a)gmail.com
<mailto:treydock@gmail.com>> wrote:
> On Wed, Aug 1, 2012 at 10:17 AM, Ofer Schreiber <oschreib(a)redhat.com
> <mailto:oschreib@redhat.com>> wrote:
>>
>>
>> ----- Original Message -----
>>> Hi all,
>>>
>>> Thanks for coming back to me Ofer.
>>>
>>> On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber
>>> <oschreib(a)redhat.com <mailto:oschreib@redhat.com>>
>>> wrote:
>>>> can you please attach the log file?
>>>> (/var/log/ovirt-engine/engine-upgrade-DATE.log)
>>>
>>> Attached is the log as requested.
>>
>> it seems that you're using a very old 3.1 build, which we never
>> released during the beta process (afair).
>> this build is a x86_64 build, which confuses the upgrade script
>> (since new rpms are noarch).
>>
>> I can't guarantee it will work fine (although I can't think of any
>> reason it won't), but using the --force-setup... parameter is a good
>> option.
>>
>> Actually, we already fixed this bug upstream, but I'm not sure it
>> will get into 3.1.
>>
>>
>>>
>>> Much appreciated.
>>>
>>> Regards.
>>>
>>> Neil Wilson.
>>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org <mailto:Users@ovirt.org>
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
> After seeing this thread I decided to attempt to reproduce the errors
> and see if I could get my same version to upgrade...
>
> This is what I have installed now,
>
> # rpm -qa ovirt*
> ovirt-engine-userportal-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-tools-common-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-genericapi-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-cli-3.1.0.2-1alpha.el6.noarch
> ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch
> ovirt-log-collector-3.1.0-11alpha.el6.noarch
> ovirt-engine-dbscripts-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-config-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-setup-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-backend-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-3.1.0_0001-1.8.el6.noarch
> ovirt-iso-uploader-3.1.0-11alpha.el6.noarch
> ovirt-image-uploader-3.1.0-11alpha.el6.noarch
> ovirt-engine-jbossas711-1-0.x86_64
> ovirt-engine-restapi-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-webadmin-portal-3.1.0_0001-1.8.el6.noarch
> ovirt-engine-notification-service-3.1.0_0001-1.8.el6.noarch
>
> However when I run engine-check-upgrade no updates are found
>
>
> # engine-check-update
> Loaded plugins: fastestmirror, priorities, versionlock
> Checking for updates... (This may take several minutes)
> Loading mirror speeds from cached hostfile
> * base: centos.mirror.lstn.net <http://centos.mirror.lstn.net>
> * epel: mirror.unl.edu <http://mirror.unl.edu>
> * extras: dallas.tx.mirror.xygenhosting.com
> * updates: mirrors.liquidweb.com <http://mirrors.liquidweb.com>
> No updates available
>
> What's strange is if I disable the versionlock plugin and check
> updates in yum , I only see 2 ovirt related items
>
> # yum --disableplugin=versionlock check-update
> Loaded plugins: fastestmirror, priorities
> Loading mirror speeds from cached hostfile
> * base: centos.mirror.lstn.net <http://centos.mirror.lstn.net>
> * epel: mirror.unl.edu <http://mirror.unl.edu>
> * extras: dallas.tx.mirror.xygenhosting.com
> * updates: mirrors.liquidweb.com <http://mirrors.liquidweb.com>
>
> <snip>
> ovirt-engine-cli.noarch
> 3.1.0.6-1.el6
>
> ovirt-dre
> ovirt-engine-sdk.noarch
> 3.1.0.4-1.el6
>
> ovirt-dre
> <snip>
>
> Have already done a 'yum clean all', and ensured my repo files match
> those posted on the website. Any tips on how to do an upgrade?
>
> Thanks
> - Trey
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Thanks
Robert Middleswarth
@rmiddle (twitter/IRC)
--------------090101000308010305080704
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">That is actually the same as
beta1. Or
the same version used on testing day. To upgrade You have to.<br>
<br>
Yum Remove ovirt-engine vdsm<br>
<br>
After all the packages are installed. Make sure you are using his
the 3.1 repo and not the devel one that is based on master but
hasn't been updated recently.<br>
<br>
Yum install ovirt-engine<br>
<br>
Run the engine-upgrade and it should give you should tell you
something about the version being the same but force-upgrade the
setup.<br>
<br>
Thanks<br>
Robert<br>
<br>
<br>
On 08/01/2012 03:11 PM, Ofer Schreiber wrote:<br>
</div>
<blockquote
cite="mid:8FAD326C-E334-430F-95E1-594571F4C0B3@redhat.com"
type="cite">
<div>
<div style="text-align: left;direction: ltr; ">Once again- you
have an unsupported version of ovirt-engine.</div>
<div style="text-align: left;direction: ltr; "><br>
</div>
<div style="text-align: left;direction: ltr; ">The reason
engine-upgrade doesn't work is that 3.1.0_0001-1>
3.1.0-2</div>
<br>
<div style="direction: rtl;"><br>
</div>
</div>
<div><br>
On 1 Aug 2012, at 21:32, Trey Dockendorf <<a
moz-do-not-send="true"
href="mailto:treydock@gmail.com">treydock@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>On Wed, Aug 1, 2012 at 10:17 AM, Ofer Schreiber
<<a
moz-do-not-send="true"
href="mailto:oschreib@redhat.com">oschreib@redhat.com</a>>
wrote:</span><br>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>----- Original Message
-----</span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Hi
all,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Thanks for coming back to
me
Ofer.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>On Tue, Jul 31, 2012 at
5:48
PM, Ofer Schreiber <<a moz-do-not-send="true"
href="mailto:oschreib@redhat.com">oschreib@redhat.com</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote
type="cite"><span>wrote:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"><span>can you please attach
the
log file?</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<blockquote
type="cite"><span>(/var/log/ovirt-engine/engine-upgrade-DATE.log)</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Attached is the log as
requested.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>it seems that you're
using a
very old 3.1 build, which we never released during the
beta process (afair).</span><br>
</blockquote>
<blockquote type="cite"><span>this build is a x86_64
build,
which confuses the upgrade script (since new rpms are
noarch).</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>I can't guarantee it
will work
fine (although I can't think of any reason it won't), but
using the --force-setup... parameter is a good
option.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Actually, we already fixed
this
bug upstream, but I'm not sure it will get into
3.1.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Much
appreciated.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote
type="cite"><span>Regards.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Neil
Wilson.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote
type="cite"><span>_______________________________________________</span><br>
</blockquote>
<blockquote type="cite"><span>Users mailing
list</span><br>
</blockquote>
<blockquote type="cite"><span><a
moz-do-not-send="true"
href="mailto:Users@ovirt.org">Users@ovirt.org</a></span><br>
</blockquote>
<blockquote type="cite"><span><a
moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</blockquote>
<span></span><br>
<span></span><br>
<span>After seeing this thread I decided to attempt to
reproduce the errors</span><br>
<span>and see if I could get my same version to
upgrade...</span><br>
<span></span><br>
<span>This is what I have installed now,</span><br>
<span></span><br>
<span># rpm -qa ovirt*</span><br>
<span>ovirt-engine-userportal-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-tools-common-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-genericapi-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-cli-3.1.0.2-1alpha.el6.noarch</span><br>
<span>ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch</span><br>
<span>ovirt-log-collector-3.1.0-11alpha.el6.noarch</span><br>
<span>ovirt-engine-dbscripts-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-config-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-setup-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-backend-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-iso-uploader-3.1.0-11alpha.el6.noarch</span><br>
<span>ovirt-image-uploader-3.1.0-11alpha.el6.noarch</span><br>
<span>ovirt-engine-jbossas711-1-0.x86_64</span><br>
<span>ovirt-engine-restapi-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-webadmin-portal-3.1.0_0001-1.8.el6.noarch</span><br>
<span>ovirt-engine-notification-service-3.1.0_0001-1.8.el6.noarch</span><br>
<span></span><br>
<span>However when I run engine-check-upgrade no updates are
found</span><br>
<span></span><br>
<span></span><br>
<span># engine-check-update</span><br>
<span>Loaded plugins: fastestmirror, priorities,
versionlock</span><br>
<span>Checking for updates... (This may take several
minutes)</span><br>
<span>Loading mirror speeds from cached hostfile</span><br>
<span> * base: <a moz-do-not-send="true"
href="http://centos.mirror.lstn.net">centos.mirror.lstn.net</a></span><br>
<span> * epel: <a moz-do-not-send="true"
href="http://mirror.unl.edu">mirror.unl.edu</a></span><br>
<span> * extras: dallas.tx.mirror.xygenhosting.com</span><br>
<span> * updates: <a moz-do-not-send="true"
href="http://mirrors.liquidweb.com">mirrors.liquidweb.com</a></span><br>
<span>No updates available</span><br>
<span></span><br>
<span>What's strange is if I disable the versionlock plugin
and check</span><br>
<span>updates in yum , I only see 2 ovirt related
items</span><br>
<span></span><br>
<span># yum --disableplugin=versionlock
check-update</span><br>
<span>Loaded plugins: fastestmirror, priorities</span><br>
<span>Loading mirror speeds from cached hostfile</span><br>
<span> * base: <a moz-do-not-send="true"
href="http://centos.mirror.lstn.net">centos.mirror.lstn.net</a></span><br>
<span> * epel: <a moz-do-not-send="true"
href="http://mirror.unl.edu">mirror.unl.edu</a></span><br>
<span> * extras: dallas.tx.mirror.xygenhosting.com</span><br>
<span> * updates: <a moz-do-not-send="true"
href="http://mirrors.liquidweb.com">mirrors.liquidweb.com</a></span><br>
<span></span><br>
<span><snip></span><br>
<span>ovirt-engine-cli.noarch</span><br>
<span>
3.1.0.6-1.el6</span><br>
<span></span><br>
<span>
ovirt-dre</span><br>
<span>ovirt-engine-sdk.noarch</span><br>
<span>
3.1.0.4-1.el6</span><br>
<span></span><br>
<span>
ovirt-dre</span><br>
<span><snip></span><br>
<span></span><br>
<span>Have already done a 'yum clean all', and ensured my repo
files match</span><br>
<span>those posted on the website. Any tips on how to do an
upgrade?</span><br>
<span></span><br>
<span>Thanks</span><br>
<span>- Trey</span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Thanks
Robert Middleswarth
@rmiddle (twitter/IRC)
</pre>
</body>
</html>
--------------090101000308010305080704--
8:47 a.m.
Hi guys,
Thank you very much for all your input and assistance.
On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber
<oschreib(a)redhat.com>
wrote:
it seems that you're using a very old 3.1 build, which we never released
during the beta process (afair).
this build is a x86_64 build, which confuses the upgrade script (since new
rpms are noarch).
I can't guarantee it will work fine (although I can't think of any reason it
won't), but using the --force-setup... parameter is a good option.
Actually, we already fixed this bug upstream, but I'm not sure it will get
into 3.1.
I'll try the --force-setup today if I get a chance, in a worst case
scenario what could go wrong?
When I run the upgrade will it create a DB backup that can be manually
restored if I have to remove all ovirt-engine packages and start from
scratch?
Anyone have some steps on how to go about restoring from the backup
that the "engine-upgrade --force-setup" creates?
Currently I'm running a two node/hypervisor setup with a SAN as my
data storage, but I can't migrate VM's between the nodes due to what
appears to be a bug, which is the reason for wanting to update the
ovirt-engine. As previously mentioned my engine is installed directly
on one of the nodes/hypervisors.
Would it perhaps be a better idea to install a new ovirt-engine onto a
different server and then migrate to the new engine rather than
updating the current one, or am I just being completely paranoid?
We are running mission critical VM's on the install, so I can't risk
something going wrong and the VM's stop running or access to them is
lost.
Thank you very much.
Regards.
Neil Wilson
9:02 a.m.
On 08/02/2012 09:47 AM, Neil wrote:
Hi guys,
Thank you very much for all your input and assistance.
> On Tue, Jul 31, 2012 at 5:48 PM, Ofer Schreiber <oschreib(a)redhat.com>
> wrote:
>
> it seems that you're using a very old 3.1 build, which we never released
> during the beta process (afair).
>
> this build is a x86_64 build, which confuses the upgrade script (since new
> rpms are noarch).
>
> I can't guarantee it will work fine (although I can't think of any reason it
> won't), but using the --force-setup... parameter is a good option.
>
> Actually, we already fixed this bug upstream, but I'm not sure it will get
> into 3.1.
I'll try the --force-setup today if I get a chance, in a worst case
scenario what could go wrong?
When I run the upgrade will it create a DB backup that can be manually
restored if I have to remove all ovirt-engine packages and start from
scratch?
Anyone have some steps on how to go about restoring from the backup
that the "engine-upgrade --force-setup" creates?
Currently I'm running a two node/hypervisor setup with a SAN as my
data storage, but I can't migrate VM's between the nodes due to what
appears to be a bug, which is the reason for wanting to update the
ovirt-engine. As previously mentioned my engine is installed directly
on one of the nodes/hypervisors.
though not directly related, that's not helping...
Would it perhaps be a better idea to install a new ovirt-engine onto a
different server and then migrate to the new engine rather than
updating the current one, or am I just being completely paranoid?
We are running mission critical VM's on the install, so I can't risk
something going wrong and the VM's stop running or access to them is
lost.
upgrade wasn't tested thourougly in these versions.
installing a new environment and moving VMs to it would be safer, but it
will require you to have more nodes, and stop/export/import/launch your VMs.
Thank you very much.
Regards.
Neil Wilson
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:59 p.m.
On Tue, Jul 31, 2012 at 1:04 PM, Itamar Heim <iheim(a)redhat.com> wrote:
you need to run the upgrade script since the setup locks the
rpm's to make
sure the code isn't updated without updating the db in sync
Thanks Itamar,
I see after running engine-check-update I get..
12 Updates available:
* ovirt-engine-3.1.0-3.15.el6.noarch
* ovirt-engine-backend-3.1.0-3.15.el6.noarch
* ovirt-engine-config-3.1.0-3.15.el6.noarch
* ovirt-engine-dbscripts-3.1.0-3.15.el6.noarch
* ovirt-engine-genericapi-3.1.0-3.15.el6.noarch
* ovirt-engine-notification-service-3.1.0-3.15.el6.noarch
* ovirt-engine-restapi-3.1.0-3.15.el6.noarch
* ovirt-engine-setup-3.1.0-3.15.el6.noarch
* ovirt-engine-tools-common-3.1.0-3.15.el6.noarch
* ovirt-engine-userportal-3.1.0-3.15.el6.noarch
* ovirt-engine-webadmin-portal-3.1.0-3.15.el6.noarch
* vdsm-bootstrap-4.10.0-0.191.9.el6.noarch
Can this update be done on a live system with multiple hosts running?
I'm currently running the engine on one of the nodes, which I know
isn't ideal.
I've searched a bit regarding the upgrade procedures from 3.1 to 3.1,
does the DB need backing up, are there any wiki pages on the correct
steps?
Thanks very much.
Regards.
Neil Wilson.
2:17 p.m.
----- Original Message -----
On Tue, Jul 31, 2012 at 1:04 PM, Itamar Heim
<iheim(a)redhat.com>
wrote:
> you need to run the upgrade script since the setup locks the rpm's
> to make
> sure the code isn't updated without updating the db in sync
Thanks Itamar,
I see after running engine-check-update I get..
12 Updates available:
* ovirt-engine-3.1.0-3.15.el6.noarch
* ovirt-engine-backend-3.1.0-3.15.el6.noarch
* ovirt-engine-config-3.1.0-3.15.el6.noarch
* ovirt-engine-dbscripts-3.1.0-3.15.el6.noarch
* ovirt-engine-genericapi-3.1.0-3.15.el6.noarch
* ovirt-engine-notification-service-3.1.0-3.15.el6.noarch
* ovirt-engine-restapi-3.1.0-3.15.el6.noarch
* ovirt-engine-setup-3.1.0-3.15.el6.noarch
* ovirt-engine-tools-common-3.1.0-3.15.el6.noarch
* ovirt-engine-userportal-3.1.0-3.15.el6.noarch
* ovirt-engine-webadmin-portal-3.1.0-3.15.el6.noarch
* vdsm-bootstrap-4.10.0-0.191.9.el6.noarch
Can this update be done on a live system with multiple hosts running?
yes.
I'm currently running the engine on one of the nodes, which I
know
isn't ideal.
I've searched a bit regarding the upgrade procedures from 3.1 to 3.1,
does the DB need backing up, are there any wiki pages on the correct
steps?
The upgrade should work fine between 3.1 to 3.1, although we never tested it.
the upgrade utility backup the entire DB before starting, feel free to backup the host
before that, since you'll probably be the first to try it.recommandedrecommanded
Thanks very much.
Regards.
Neil Wilson.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3:16 p.m.
On Tue, Jul 31, 2012 at 2:17 PM, Ofer Schreiber <oschreib(a)redhat.com> wrote:
The upgrade should work fine between 3.1 to 3.1, although we never
tested it.
the upgrade utility backup the entire DB before starting, feel free to backup the host
before that, since you'll probably be the first to > try it.
Thank you Ofer,
I'm not sure what you mean by "...to backup the host before that." in
what way should I backup the host, and what do you refer to when you
say host?
Thank you, my apologies for the confusion.
Regards.
Neil Wilson.
3:29 p.m.
----- Original Message -----
On Tue, Jul 31, 2012 at 2:17 PM, Ofer Schreiber
<oschreib(a)redhat.com>
wrote:
> The upgrade should work fine between 3.1 to 3.1, although we never
> tested it.
> the upgrade utility backup the entire DB before starting, feel free
> to backup the host before that, since you'll probably be the first
> to > try it.
Thank you Ofer,
I'm not sure what you mean by "...to backup the host before that."
in
what way should I backup the host, and what do you refer to when you
say host?
iiuc, the engine is inside a vm, so a simple disk snapshot would be optimal.
if not - any other method of backing up the host in which the engine is installed is
enough (lvm snapshot for example).
You can backup only the db - it's just a matter of how critical is your environment
(and the ease of revert)
Thank you, my apologies for the confusion.
Regards.
Neil Wilson.
3:31 p.m.
On 07/31/2012 08:17 AM, Ofer Schreiber wrote:
----- Original Message -----
> On Tue, Jul 31, 2012 at 1:04 PM, Itamar Heim <iheim(a)redhat.com>
> wrote:
>
>> you need to run the upgrade script since the setup locks the rpm's
>> to make
>> sure the code isn't updated without updating the db in sync
> Thanks Itamar,
>
> I see after running engine-check-update I get..
>
> 12 Updates available:
> * ovirt-engine-3.1.0-3.15.el6.noarch
> * ovirt-engine-backend-3.1.0-3.15.el6.noarch
> * ovirt-engine-config-3.1.0-3.15.el6.noarch
> * ovirt-engine-dbscripts-3.1.0-3.15.el6.noarch
> * ovirt-engine-genericapi-3.1.0-3.15.el6.noarch
> * ovirt-engine-notification-service-3.1.0-3.15.el6.noarch
> * ovirt-engine-restapi-3.1.0-3.15.el6.noarch
> * ovirt-engine-setup-3.1.0-3.15.el6.noarch
> * ovirt-engine-tools-common-3.1.0-3.15.el6.noarch
> * ovirt-engine-userportal-3.1.0-3.15.el6.noarch
> * ovirt-engine-webadmin-portal-3.1.0-3.15.el6.noarch
> * vdsm-bootstrap-4.10.0-0.191.9.el6.noarch
>
> Can this update be done on a live system with multiple hosts running?
yes.
> I'm currently running the engine on one of the nodes, which I know
> isn't ideal.
> I've searched a bit regarding the upgrade procedures from 3.1 to 3.1,
> does the DB need backing up, are there any wiki pages on the correct
> steps?
The upgrade should work fine between 3.1 to 3.1, although we never tested it.
the upgrade utility backup the entire DB before starting, feel free to backup the host
before that, since you'll probably be the first to try it.recommandedrecommanded
I have used it several times. The 1st time I tired it failed badly but
I upgrade the wrong way. AKA I uninstalled the old packages and
installed new once when the format of the packages changed. However
since then I have done upgrade using engine-upgrade twice without issue.
> Thanks very much.
>
> Regards.
>
> Neil Wilson.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Thanks
Robert Middleswarth
@rmiddle (twitter/IRC)
4290
days inactive
4292
days old
16 comments
5 participants
participants (5)
-
Itamar Heim -
Neil -
Ofer Schreiber -
Robert Middleswarth -
Trey Dockendorf