4:33 a.m.
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