[ovirt-users] necessity to run yum update ovirt-engine-setup to update ovirt 3.4

[Yedidyah Bar David]

(Mail sent to me privately; replying also to the list)

----- Original Message -----
> From: "Tamer Lima" <tamer.americo at gmail.com>
> To: "Yedidyah Bar David" <didi at redhat.com>
> Sent: Thursday, April 10, 2014 4:30:11 PM
> Subject: Re: [ovirt-users] necessity to run yum update ovirt-engine-setup to update ovirt 3.4
> 
> Hello, mister
> 
> 
> 
> On Thu, Apr 10, 2014 at 3:29 AM, Yedidyah Bar David <didi at redhat.com> wrote:
> 
> > ----- Original Message -----
> > > From: "Tamer Lima" <tamer.americo at gmail.com>
> > > To: users at 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.
> >
> >
> I followed this anchor :
> http://www.ovirt.org/OVirt_3.4_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL
> 
> ====================
> 
> If you're upgrading from oVirt 3.3 you should just execute:
> 
>     # yum update ovirt-engine-setup
>     # engine-setup
> 
> ==========================
> 
> 
> 
> > >
> > > 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.
> >
> >
> Well, according the output on prompt shell, there was no update : "No
> Packages marked for Update"

Obviously, if it's already updated by your cron.

> 
> 
> >  >
> > > 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.
> >
> > >
> > >
> >
> 
> ok. thanks .
> 
> > >
> > >
> > >
> > > 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.
> >
> >
> you are right. thanks. on april,6 my yumcron updated ovirt to 3.4.  (just
> update, not setup)
> 
> 
> [root at srv-0202 ~]# more  /var/log/yum.log  | grep ovirt
> Feb 27 13:08:05 Installed: ovirt-release-11.0.2-1.noarch
> Feb 27 13:52:17 Installed: ovirt-engine-sdk-python-3.3.3.0-1.el6.noarch
> Feb 27 13:52:18 Installed: ovirt-host-deploy-1.1.3-1.el6.noarch
> Feb 27 13:52:22 Installed: ovirt-image-uploader-3.3.3-1.el6.noarch
> Feb 27 13:52:22 Installed: ovirt-iso-uploader-3.3.3-1.el6.noarch
> Feb 27 13:52:23 Installed: ovirt-engine-lib-3.3.3-2.el6.noarch
> Feb 27 13:52:23 Installed: ovirt-engine-websocket-proxy-3.3.3-2.el6.noarch
> Feb 27 13:52:36 Installed: ovirt-log-collector-3.3.3-1.el6.noarch
> Feb 27 13:52:36 Installed: ovirt-host-deploy-java-1.1.3-1.el6.noarch
> Feb 27 13:53:16 Installed: ovirt-engine-cli-3.3.0.6-1.el6.noarch
> Feb 27 13:53:19 Installed: ovirt-engine-userportal-3.3.3-2.el6.noarch
> Feb 27 13:53:26 Installed: ovirt-engine-webadmin-portal-3.3.3-2.el6.noarch
> Feb 27 13:53:26 Installed: ovirt-engine-dbscripts-3.3.3-2.el6.noarch
> Feb 27 13:53:26 Installed: ovirt-engine-restapi-3.3.3-2.el6.noarch
> Feb 27 13:53:26 Installed: ovirt-engine-tools-3.3.3-2.el6.noarch
> Feb 27 13:53:26 Installed: ovirt-engine-setup-3.3.3-2.el6.noarch
> Feb 27 13:53:27 Installed: ovirt-engine-backend-3.3.3-2.el6.noarch
> Feb 27 13:53:27 Installed: ovirt-engine-3.3.3-2.el6.noarch
> Feb 27 13:53:59 Installed: ovirt-host-deploy-offline-1.1.3-1.el6.noarch
> Feb 27 13:53:59 Installed:
> ovirt-engine-setup-plugin-allinone-3.3.3-2.el6.noarch
> 
> Apr 06 04:21:12 Updated: ovirt-engine-sdk-python-3.4.0.6-1.el6.noarch
> Apr 06 04:21:12 Updated: ovirt-engine-lib-3.4.0-1.el6.noarch
> Apr 06 04:21:13 Installed: ovirt-engine-setup-base-3.4.0-1.el6.noarch
> Apr 06 04:21:13 Updated: ovirt-host-deploy-1.2.0-1.el6.noarch
> Apr 06 04:21:38 Installed:
> ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch
> Apr 06 04:21:38 Installed:
> ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch
> Apr 06 04:21:38 Installed:
> ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch
> Apr 06 04:22:00 Updated: ovirt-host-deploy-offline-1.2.0-1.el6.x86_64
> Apr 06 04:22:00 Updated:
> ovirt-engine-setup-plugin-allinone-3.4.0-1.el6.noarch
> Apr 06 04:22:00 Updated: ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch
> Apr 06 04:22:00 Updated: ovirt-host-deploy-java-1.2.0-1.el6.noarch
> Apr 06 04:22:00 Updated: ovirt-engine-setup-3.4.0-1.el6.noarch
> Apr 06 04:22:02 Updated: ovirt-log-collector-3.4.1-1.el6.noarch
> Apr 06 04:22:02 Updated: ovirt-image-uploader-3.4.0-1.el6.noarch
> Apr 06 04:22:02 Updated: ovirt-engine-cli-3.4.0.5-1.el6.noarch
> Apr 06 04:22:02 Updated: ovirt-iso-uploader-3.4.0-1.el6.noarch
> Apr 06 04:22:08 Updated: ovirt-release-11.1.0-1.noarch
> Apr 09 11:46:08 Updated: ovirt-engine-dbscripts-3.4.0-1.el6.noarch
> Apr 09 11:46:16 Updated: ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch
> Apr 09 11:46:17 Updated: ovirt-engine-backend-3.4.0-1.el6.noarch
> Apr 09 11:46:17 Updated: ovirt-engine-restapi-3.4.0-1.el6.noarch
> Apr 09 11:46:17 Updated: ovirt-engine-tools-3.4.0-1.el6.noarch
> Apr 09 11:46:17 Updated: ovirt-engine-3.4.0-1.el6.noarch
> Apr 09 11:46:24 Updated: ovirt-engine-userportal-3.4.0-1.el6.noarch
> Apr 10 03:27:27 Updated: ovirt-release-11.2.0-1.noarch
> 
> 
> 
> in fact,  the 2 steps are correct  : first update with yum , then finally
> execute engine-setup.
> 
> Now I am thinking about it.
> I have to verify yum updates, because my system can be updated a long
> without my knowledge,
> but is mandatory to make a setup after this update. otherwise, in practice
> ovirt is not well deployed, right  ?

Not sure what you ask exactly.

If it's "I want to keep my system automatically up-to-date all the time.
What should I do?", then, yes, you are right. 'yum update' is not enough,
you also need to run engine-setup. I would not recommend to do that in
cron - you might want to make a cron job that alerts you somehow if there
are updates, but actually run 'engine-setup' manually. That said, generally
speaking, during a specific version, the questions and answers asked during
upgrade are not changed, so you can create an answer file for e.g. 3.4
updates, verify that engine-setup with this answer file works as expected,
and run it from cron.

If it's "I run yum update in cron. I understand that I also need to run
engine-setup to update the engine. Should I expect any damage from not
doing that - that is, having updated packages without running engine-setup?",
then no, the packages that are sensitive to database content are version-locked,
and will not be updated by a normal yum update.

Best regards,
-- 
Didi