Il giorno lun 21 dic 2020 alle ore 18:08 Gianluca Cecchi < [email protected]> ha scritto:
> On Mon, Dec 21, 2020 at 2:36 PM Sandro Bonazzola <[email protected]> > wrote: > >> >> >> Il giorno lun 21 dic 2020 alle ore 14:31 Gianluca Cecchi < >> [email protected]> ha scritto: >> >>> Hi Sandro, >>> thanks for the release! >>> >>> Should this fix the upgrade problems to cluster version 4.5 too when >>> using CentOS 8.3 + updates? >>> >> >> Yes >> >> >> > Hi Sandro, > I confirm that on a test cluster with 3 plain CentOS 8.3 hosts and an > external CentOS 8.3 based engine I was able to update all of them to 4.4.4 > and then update both cluster and DC level to 4.5. > Can you recall, apart from being now at the latest level, what kind of new > features I should expect in 4.5 vs 4.4 so that I can also test and use them > for improvements (eg in storage domain version/features, incremental > backup, snapshotting features, export and such...)? > Cluster compatibility level has been introduced with: *Bug 1877675* <https://bugzilla.redhat.com/show_bug.cgi?id=1877675> - [RFE] Introduce Datacenter and cluster level 4.5 It tracks: *- Bug 1725166 <https://bugzilla.redhat.com/show_bug.cgi?id=1725166> - [RFE] Private VLAN / port isolation* *- Support for Intel Icelake Server Family * *- **Bug 1814565* <https://bugzilla.redhat.com/show_bug.cgi?id=1814565> - Report disk.usage for VMs with RHEL 8 guests - *Bug 1852718* <https://bugzilla.redhat.com/show_bug.cgi?id=1852718> - vGPU: VM failed to run with mdev_type instance - *Bug 1853194* <https://bugzilla.redhat.com/show_bug.cgi?id=1853194> - VM with disk on iscsi on environment with SELinux enforced fails to start on host - Exit message: Wake up from hibernation failed:internal error: child reported (status=125): unable to set security context - *Bug 1876605* <https://bugzilla.redhat.com/show_bug.cgi?id=1876605> - VM with scsi hostdev (scsi_generic custom property) fails on start:'node-name too long for qemu' +Martin Perina <[email protected]> , +Arik Hadas <[email protected]> , +Tal Nisan <[email protected]> , +Dominik Holler <[email protected]> feel free to add if I missed something. I think that having a page on oVirt documentation with features and requirements per supported cluster compatibility level would help. Gianluca, maybe you can open a bug for it? > > thanks > Gianluca > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> [email protected] <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/SGK5DZGIGA6FO3NK2USMXHBYVH5QRN7M/
