2) Command to upgrade the engine

In oVirt page we have

yum update "ovirt-engine-setup*"

In RHEV we have the command without the star

yum update ovirt-engine-setup

If I remember correctly the star was important in the past.... 

Any comments on this difference? Documentation error or different functionalities or dependency chain changed so that now it is not necessary the star also in oVirt?

Being on RHEL 7 OS with 4.0.4 they seems now equivalent

- yum update ovirt-engine-setup

Dependencies Resolved

====================================================================================================

 Package                                           Arch    Version                 Repository  Size

====================================================================================================

Updating:

 ovirt-engine-setup                                noarch  4.0.5.5-1.el7.centos    ovirt-4.0   10 k

Updating for dependencies:

 ovirt-engine-lib                                  noarch  4.0.5.5-1.el7.centos    ovirt-4.0   29 k

 ovirt-engine-setup-base                           noarch  4.0.5.5-1.el7.centos    ovirt-4.0   97 k

 ovirt-engine-setup-plugin-ovirt-engine            noarch  4.0.5.5-1.el7.centos    ovirt-4.0  165 k

 ovirt-engine-setup-plugin-ovirt-engine-common     noarch  4.0.5.5-1.el7.centos    ovirt-4.0   83 k

 ovirt-engine-setup-plugin-vmconsole-proxy-helper  noarch  4.0.5.5-1.el7.centos    ovirt-4.0   28 k

 ovirt-engine-setup-plugin-websocket-proxy         noarch  4.0.5.5-1.el7.centos    ovirt-4.0   27 k

Transaction Summary

====================================================================================================

Upgrade  1 Package (+6 Dependent packages)

- yum update "ovirt-engine-setup*"

Dependencies Resolved

====================================================================================================

 Package                                           Arch    Version                 Repository  Size

====================================================================================================

Updating:

 ovirt-engine-setup                                noarch  4.0.5.5-1.el7.centos    ovirt-4.0   10 k

 ovirt-engine-setup-base                           noarch  4.0.5.5-1.el7.centos    ovirt-4.0   97 k

 ovirt-engine-setup-plugin-ovirt-engine            noarch  4.0.5.5-1.el7.centos    ovirt-4.0  165 k

 ovirt-engine-setup-plugin-ovirt-engine-common     noarch  4.0.5.5-1.el7.centos    ovirt-4.0   83 k

 ovirt-engine-setup-plugin-vmconsole-proxy-helper  noarch  4.0.5.5-1.el7.centos    ovirt-4.0   28 k

 ovirt-engine-setup-plugin-websocket-proxy         noarch  4.0.5.5-1.el7.centos    ovirt-4.0   27 k

Updating for dependencies:

 ovirt-engine-lib                                  noarch  4.0.5.5-1.el7.centos    ovirt-4.0   29 k

Transaction Summary

====================================================================================================

Upgrade  6 Packages (+1 Dependent package)

Total download size: 440 k

Is this ok [y/d/N]: 

BTW:

In my opinion it is not clear in RHEV documentation that if you have a Self Hosted Engine environment you have to put global maintenance before upgrading engine.

Inside the Upgrade Guide it is only covered the specific case when you migrate from 3.6 to 4.0 the Self Hosted Engine, while in minor upgrades at

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/upgrade-guide/chapter-2-updates-between-minor-releases

it is not specified.

Inside the Self Hosted Engine guide at 

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/self-hosted-engine-guide/chapter-5-maintenance-and-upgrading-resources  

when describing maintenance modes it is indeed specified 

"

The global maintenance mode must be applied for any setup or upgrade operations that require the engine to be stopped, such as upgrading to a later version of Red Hat Virtualization.

"

but in my opinion it should be put in clear also inside the Upgrade Guide.

In case let me know how can I open a documentation bug for this if you agree.

Gianluca

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