On 04/09/2014 09:18 PM, Tamer Lima wrote:

hello,

upgrade from ovirt 3.3 to 3.4 following the steps on ovirt.org/OVirt_3.4_Release_Notes <http://ovirt.org/OVirt_3.4_Release_Notes>

I tried update from yum, without success

yum update {ovirt-engine-setup, ovirt-engine , ovirt-release and ovirt-release-el6 }

Then I tried the following command and it worked fine: engine-setup

Now my ovirt works fine, my cluster is running virtual machines on compatibility mode 3.3 although ovirt is now 3.4

Then I ask : What is the necessity to execute *yum update ovirt-engine-setup* if when I execute only *engine-setup* this script search for updates ?

to make sure you are running the latest engine-setup code.

Failed command list execution For each command /yum update {ovirt-engine-setup, ovirt-engine , ovirt-release and ovirt-release-el6 }/ the result was the same :

Loaded plugins: downloadonly, fastestmirror, refresh-packagekit, security, versionlock Loading mirror speeds from cached hostfile * base: mirror.globo.com <http://mirror.globo.com> * epel: mirror.globo.com <http://mirror.globo.com> * extras: mirror.globo.com <http://mirror.globo.com> * ovirt-epel: mirror.globo.com <http://mirror.globo.com> * updates: mirror.globo.com <http://mirror.globo.com> Setting up Update Process *No Packages marked for Update*

My ovirt.repo contains 3.4 : [root@srv-0202 yum.repos.d]# more ovirt.repo

[ovirt-stable] name=Latest oVirt Releases baseurl=http://ovirt.org/releases/stable/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0

# Latest oVirt 3.4 releases

[ovirt-3.4-stable] name=Latest oVirt 3.4.z Releases baseurl=http://ovirt.org/releases/3.4/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0

[ovirt-3.4-prerelease] name=Latest oVirt 3.4 Pre Releases (Beta to Release Candidate) baseurl=http://resources.ovirt.org/releases/3.4_pre/rpm/EL/$releasever/ enabled=0 skip_if_unavailable=1 gpgcheck=0

# Latest oVirt 3.3 releases

[ovirt-3.3-stable] name=Latest oVirt 3.3.z Releases baseurl=http://resources.ovirt.org/releases/3.3/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0

[ovirt-3.3-prerelease] name=Latest oVirt 3.3.z Pre Releases (Beta to Release Candidate) baseurl=http://resources.ovirt.org/releases/3.3_pre/rpm/EL/$releasever/ enabled=0 skip_if_unavailable=1 gpgcheck=0

# Note: for nightly builds see ovirt-nightly.repo

Running engine-setup [root@srv-0202 ~]# engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf', '/etc/ovirt-engine-setup.conf.d/10-pa ckaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-aio.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140409114215.log Version: otopi-1.2.0 (otopi-1.2.0-1.el6) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Stage: Environment customization

--== PRODUCT OPTIONS ==--

--== PACKAGES ==--

*[ INFO ] Checking for product updates...* * Setup has found updates for some packages, do you wish to update them now? (Yes, No) [Yes]: yes* [ INFO ] Checking for an update for Setup...

--== NETWORK CONFIGURATION ==--

Setup can automatically configure the firewall on this system. Note: automatic configuration of the firewall may overwrite current settings. Do you want Setup to configure the firewall? (Yes, No) [Yes]: no

--== DATABASE CONFIGURATION ==--

--== OVIRT ENGINE CONFIGURATION ==--

Skipping storing options as database already prepared

--== PKI CONFIGURATION ==--

PKI is already configured

--== APACHE CONFIGURATION ==--

--== SYSTEM CONFIGURATION ==--

--== MISC CONFIGURATION ==--

--== END OF CONFIGURATION ==--

[ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ INFO ] Cleaning stale zombie tasks

--== CONFIGURATION PREVIEW ==--

Engine database name : engine Engine database secured connection : False Engine database host : localhost Engine database user name : engine Engine database host name validation : False Engine database port : 5432 NFS setup : True Firewall manager : iptables Update Firewall : False Configure WebSocket Proxy : True Host FQDN : srv-0202.ltitd.br <http://srv-0202.ltitd.br> NFS mount point : /var/lib/exports/iso Set application as default page : True Configure Apache SSL : True Upgrade packages : True

Please confirm installation settings (OK, Cancel) [OK]: [ INFO ] Cleaning async tasks and compensations [ INFO ] Checking the Engine database consistency [ INFO ] Stage: Transaction setup [ INFO ] Stopping engine service [ INFO ] Stopping websocket-proxy service [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Yum Status: Downloading Packages *[ INFO ] Yum Download/Verify: ovirt-engine-3.4.0-1.el6.noarch* [ INFO ] Yum Download/Verify: ovirt-engine-backend-3.4.0-1.el6.noarch [ INFO ] Yum Download/Verify: ovirt-engine-dbscripts-3.4.0-1.el6.noarch [ INFO ] Yum Download/Verify: ovirt-engine-restapi-3.4.0-1.el6.noarch [ INFO ] Yum Download/Verify: ovirt-engine-tools-3.4.0-1.el6.noarch [ INFO ] Yum Downloading: (6/7): ovirt-engine-userportal-3.4.0-1.el6.noarch.rpm 54 M(66%) [ INFO ] Yum Download/Verify: ovirt-engine-userportal-3.4.0-1.el6.noarch [ INFO ] Yum Downloading: (7/7): ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch.rpm 37 M(35%) [ INFO ] Yum Download/Verify: ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch [ INFO ] Yum Status: Check Package Signatures [ INFO ] Yum Status: Running Test Transaction [ INFO ] Yum Status: Running Transaction [ INFO ] Yum update: 1/14: ovirt-engine-dbscripts-3.4.0-1.el6.noarch [ INFO ] Yum update: 2/14: ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch [ INFO ] Yum update: 3/14: ovirt-engine-backend-3.4.0-1.el6.noarch [ INFO ] Yum update: 4/14: ovirt-engine-restapi-3.4.0-1.el6.noarch [ INFO ] Yum update: 5/14: ovirt-engine-tools-3.4.0-1.el6.noarch *[ INFO ] Yum update: 6/14: ovirt-engine-3.4.0-1.el6.noarch* [ INFO ] Yum update: 7/14: ovirt-engine-userportal-3.4.0-1.el6.noarch [ INFO ] Yum updated: 8/14: ovirt-engine-backend [ INFO ] Yum updated: 9/14: ovirt-engine-dbscripts [ INFO ] Yum updated: 10/14: ovirt-engine-restapi [ INFO ] Yum updated: 11/14: ovirt-engine-tools [ INFO ] Yum updated: 12/14: ovirt-engine-webadmin-portal [ INFO ] Yum updated: 13/14: ovirt-engine [ INFO ] Yum updated: 14/14: ovirt-engine-userportal [ INFO ] Yum Verify: 1/14: ovirt-engine-userportal.noarch 0:3.4.0-1.el6 - u [ INFO ] Yum Verify: 2/14: ovirt-engine-dbscripts.noarch 0:3.4.0-1.el6 - u [ INFO ] Yum Verify: 3/14: ovirt-engine-webadmin-portal.noarch 0:3.4.0-1.el6 - u [ INFO ] Yum Verify: 4/14: ovirt-engine-backend.noarch 0:3.4.0-1.el6 - u [ INFO ] Yum Verify: 5/14: ovirt-engine-restapi.noarch 0:3.4.0-1.el6 - u *[ INFO ] Yum Verify: 6/14: ovirt-engine.noarch 0:3.4.0-1.el6 - u* [ INFO ] Yum Verify: 7/14: ovirt-engine-tools.noarch 0:3.4.0-1.el6 - u [ INFO ] Yum Verify: 8/14: ovirt-engine.noarch 0:3.3.3-2.el6 - ud [ INFO ] Yum Verify: 9/14: ovirt-engine-restapi.noarch 0:3.3.3-2.el6 - ud [ INFO ] Yum Verify: 10/14: ovirt-engine-backend.noarch 0:3.3.3-2.el6 - ud [ INFO ] Yum Verify: 11/14: ovirt-engine-webadmin-portal.noarch 0:3.3.3-2.el6 - ud [ INFO ] Yum Verify: 12/14: ovirt-engine-dbscripts.noarch 0:3.3.3-2.el6 - ud [ INFO ] Yum Verify: 13/14: ovirt-engine-userportal.noarch 0:3.3.3-2.el6 - ud [ INFO ] Yum Verify: 14/14: ovirt-engine-tools.noarch 0:3.3.3-2.el6 - ud [ INFO ] Stage: Misc configuration *[ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20140409114625.Yw3E9y.sql'.* [ INFO ] Updating Engine database schema [ INFO ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up

--== SUMMARY ==--

SSH fingerprint: BF:60:C4:9B:C3:3D:E5:93:C0:65:0B:EB:CF:F8:63:34 Internal CA 30:29:3E:F8:87:6F:38:7B:F3:A9:39:56:27:B1:6E:3F:08:5D:FD:33 Web access is enabled at: http://srv-0202.lttd.br:80/ovirt-engine https://srv-0202.lttd.br:443/ovirt-engine

--== END OF SUMMARY ==--

[ INFO ] Starting engine service [ INFO ] Restarting httpd [ INFO ] Restarting nfs services [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140409114634-setup.conf' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140409114215.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of setup completed successfully

tamer

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

----- Original Message -----

From: "Tamer Lima" <tamer.americo@gmail.com> To: users@ovirt.org Sent: Wednesday, April 9, 2014 9:18:51 PM Subject: [ovirt-users] necessity to run yum update ovirt-engine-setup to update ovirt 3.4

hello,

upgrade from ovirt 3.3 to 3.4 following the steps on ovirt.org/OVirt_3.4_Release_Notes

I tried update from yum, without success

yum update {ovirt-engine-setup, ovirt-engine , ovirt-release and ovirt-release-el6 }

Where do you see instructions to update ovirt-engine? You cannot update it directly because it's version-locked. This is done to ensure that you do not run a newer engine with an older database - the main task engine-setup does during an upgrade is updating the database.

Then I tried the following command and it worked fine: engine-setup

Didn't it tell you that there are updates to Setup and that you should first 'yum update ovirt-engine-setup'? Probably during your attempts you did update it.

Now my ovirt works fine, my cluster is running virtual machines on compatibility mode 3.3 although ovirt is now 3.4

Great :-)

Then I ask : What is the necessity to execute yum update ovirt-engine-setup if when I execute only engine-setup this script search for updates ?

engine-setup searches for both updates to the engine and to Setup itself. If it finds updates to Setup, it tells you to manually update it with yum. If it finds other updates it asks you to confirm updating and then updates.

Failed command list execution For each command yum update {ovirt-engine-setup, ovirt-engine , ovirt-release and ovirt-release-el6 } the result was the same :

Loaded plugins: downloadonly, fastestmirror, refresh-packagekit, security, versionlock Loading mirror speeds from cached hostfile * base: mirror.globo.com * epel: mirror.globo.com * extras: mirror.globo.com * ovirt-epel: mirror.globo.com * updates: mirror.globo.com Setting up Update Process No Packages marked for Update

Most probably you did update ovirt-engine-setup at some point. If you want to further debug this, please look at and/or post your yum.log. Best regards, -- Didi