Comparing upgrade guide between oVirt and RHEV
Hello, I'm just noticing changes in web page for release notes of oVirt 4.0.5: http://www.ovirt.org/release/4.0.5/ There are now several links to the corresponding official RHEV documents. I think this is good, especially if they remains not so far each other. I just noticed 2 things: 1) the command engine-upgrade-check That I didn't know and seems to work quite good in oVirt 4.0.4 It gives me [root@ractorshe ~]# yum clean all Loaded plugins: fastestmirror, versionlock Repository virtio-win-stable is listed more than once in the configuration Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast Cleaning repos: base centos-ovirt36 centos-ovirt40-release epel extras ovirt-3.6 : ovirt-3.6-centos-gluster37 ovirt-3.6-epel ovirt-3.6-patternfly1-noarch-epel : ovirt-4.0 ovirt-4.0-centos-gluster37 ovirt-4.0-epel : ovirt-4.0-patternfly1-noarch-epel updates virtio-win-stable Cleaning up everything Cleaning up list of fastest mirrors [root@ractorshe ~]# engine-upgrade-check VERB: queue package ovirt-engine-setup for update VERB: Downloading: epel/x86_64/metalink (0%) VERB: Downloading: epel/x86_64/metalink 24 k(100%) VERB: Downloading: ovirt-3.6-epel/x86_64/metalink (0%) VERB: Downloading: ovirt-3.6-epel/x86_64/metalink 24 k(100%) VERB: Downloading: ovirt-4.0-epel/x86_64/metalink (0%) VERB: Downloading: ovirt-4.0-epel/x86_64/metalink 24 k(100%) VERB: Downloading: base/7/x86_64 (0%) ... VERB: Downloading: virtio-win-stable 3.0 k(100%) VERB: Downloading: virtio-win-stable/primary_db (0%) VERB: Downloading: virtio-win-stable/primary_db 2.3 k(100%) VERB: processing package ovirt-engine-setup-4.0.5.5-1.el7.centos.noarch for update VERB: package ovirt-engine-setup-4.0.5.5-1.el7.centos.noarch queued VERB: Building transaction VERB: Transaction built VERB: Transaction Summary: VERB: updated - ovirt-engine-lib-4.0.4.4-1.el7.centos.noarch VERB: update - ovirt-engine-lib-4.0.5.5-1.el7.centos.noarch VERB: updated - ovirt-engine-setup-4.0.4.4-1.el7.centos.noarch VERB: update - ovirt-engine-setup-4.0.5.5-1.el7.centos.noarch VERB: updated - ovirt-engine-setup-base-4.0.4.4-1.el7.centos.noarch VERB: update - ovirt-engine-setup-base-4.0.5.5-1.el7.centos.noarch VERB: updated - ovirt-engine-setup-plugin-ovirt-engine-4.0.4.4-1.el7.centos.noarch VERB: update - ovirt-engine-setup-plugin-ovirt-engine-4.0.5.5-1.el7.centos.noarch VERB: updated - ovirt-engine-setup-plugin-ovirt-engine-common-4.0.4.4-1.el7.centos.noarch VERB: update - ovirt-engine-setup-plugin-ovirt-engine-common-4.0.5.5-1.el7.centos.noarch VERB: updated - ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.4.4-1.el7.centos.noarch VERB: update - ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.5.5-1.el7.centos.noarch VERB: updated - ovirt-engine-setup-plugin-websocket-proxy-4.0.4.4-1.el7.centos.noarch VERB: update - ovirt-engine-setup-plugin-websocket-proxy-4.0.5.5-1.el7.centos.noarch Upgrade available 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? Thanks, Gianluca
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/... it is not specified. Inside the Self Hosted Engine guide at https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/... 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
On Tue, Nov 15, 2016 at 1:16 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
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
Both of them could be wrong if in the past you installed DWH. The right one is: yum update ovirt-*-setup* I'm triggering the procedures to fix the two documents.
- 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.
You are more than welcome. Thanks!
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, Nov 15, 2016 at 2:19 PM, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Tue, Nov 15, 2016 at 1:16 PM, Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
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
Both of them could be wrong if in the past you installed DWH. The right one is: yum update ovirt-*-setup*
I'm triggering the procedures to fix the two documents.
right. But at least you are notified when you run engine-setup. In my case during engine-setup I got: [ INFO ] Checking for an update for Setup... An update for the Setup packages ovirt-engine-dwh-setup was found. Please update that package by running: "yum update ovirt-engine-dwh-setup" and then execute Setup again. [ ERROR ] Failed to execute stage 'Environment customization': Please update the Setup packages [ INFO ] Stage: Clean up Then yum update ovirt-engine-dwh-setup and then upgrade with "engine-setup" again went ok
In case let me know how can I open a documentation bug for this if you
agree.
You are more than welcome. Thanks!
Against what?
On Tue, Nov 15, 2016 at 2:46 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
In case let me know how can I open a documentation bug for this if you
agree.
You are more than welcome. Thanks!
Against what?
Created this one https://bugzilla.redhat.com/show_bug.cgi?id=1395294 Feel free to edit if I missed anything Gianluca
participants (2)
-
Gianluca Cecchi -
Simone Tiraboschi