2018-02-13 11:42 GMT+01:00 Alex K <rightkicktech@gmail.com>:Hi all,Is this version considered production ready?Yes, 4.2.1 is considered production readyAlexThanx,On Mon, Feb 12, 2018 at 7:14 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:______________________________2018-02-12 17:43 GMT+01:00 Gianluca Cecchi <gianluca.cecchi@gmail.com>:On Mon, Feb 12, 2018 at 4:22 PM, Lev Veyde <lveyde@redhat.com> wrote:The oVirt Project is pleased to announce the availability of the oVirt 4.. , as of th, 201This update is the in a series of stabilization updates to the 4.series.This release is available now for:* Red Hat Enterprise Linux 7.4 or later* CentOS Linux (or similar) 7.4 or laterThis release supports Hypervisor Hosts running:* Red Hat Enterprise Linux 7.4 or later* CentOS Linux (or similar) 7.4 or later* oVirt Node 4.Hello,could you confirm that for plain CentOS 7.4 hosts there was no changes between rc3 and final 4.2.1?We had 3 RC after RC3, last one was RC6 https://lists.ovirt.org/pipermail/announce/2018-February /000387.html I just updated an environment that was in RC3 and while the engine has been updated, the host says no updates:[root@ov42 ~]# yum updateLoaded plugins: fastestmirror, langpacks, product-id, search-disabled-reposLoading mirror speeds from cached hostfile* base: artfiles.org* extras: ba.mirror.garr.it* ovirt-4.2: ftp.nluug.nl* ovirt-4.2-epel: epel.besthosting.ua* updates: ba.mirror.garr.itNo packages marked for updateI think mirrors are still syncing, but resources.ovirt.org is updated.You can switch from mirrorlist to baseurl in your yum config file if you don't want to wait for the mirror to finish the sync.[root@ov42 ~]#The mirrors seem the same that the engine has used some minutes before, so they should be ok...engine packages passed from ovirt-engine-4.2.1.4-1.el7.centos.noarch to ovirt-engine-4.2.1.6-1.el7. centos.noarch Base oVirt related packages on host are currently of this type, since 4.2.1rc3:libvirt-daemon-3.2.0-14.el7_4.7.x86_64 ovirt-host-4.2.1-1.el7.centos.x86_64 qemu-kvm-ev-2.9.0-16.el7_4.13.1.x86_64 sanlock-3.5.0-1.el7.x86_64vdsm-4.20.17-1.el7.centos.x86_64 virt-v2v-1.36.3-6.el7_4.3.x86_64 yes, most of the changes in the last 3 rcs were related to cockpit-ovirt / ovirt-node / hosted engine$ cat ovirt-4.2.1_rc4.conf ovirt-4.2.1_rc5.conf ovirt-4.2.1_rc6.conf ovirt-4.2.1.conf# ovirt-engine-4.2.1.4# cockpit-ovirt-0.11.7-0.1# ovirt-release42-4.2.1_rc4# otopi-1.7.7# ovirt-host-deploy-1.7.2# ovirt-hosted-engine-setup-2.2.9 # cockpit-ovirt-0.11.11-0.1# ovirt-release42-4.2.1_rc5# ovirt-engine-appliance-4.2-20180202.1 # ovirt-node-ng-4.2.0-0.20180205.0 # ovirt-engine-4.2.1.5# ovirt-engine-4.2.1.6# ovirt-release42-4.2.1_rc6# ovirt-release42-4.2.1Thanks,Gianluca
_______________________________________________
Announce mailing list
Announce@ovirt.org
http://lists.ovirt.org/mailman/listinfo/announce
--
_________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users