Re: [ovirt-devel] [ANN] oVirt 4.2.0 Second Candidate Release is now available for testing

On Wed, Dec 13, 2017 at 11:40 AM, Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > > > 2017-12-13 11:37 GMT+01:00 Michal Skrivanek <michal.skrivanek(a)redhat.com&gt; > : > >> >> > On 13 Dec 2017, at 09:58, Sandro Bonazzola <sbonazzo(a)redhat.com&gt; >> wrote: >> > >> > >> > >> > 2017-12-13 9:51 GMT+01:00 Michal Skrivanek < >> michal.skrivanek(a)redhat.com&gt;: >> > Hi Sandro, >> > we’ve identified one more blocker for HE installations[1]. We plan >> getting it in today if everything goes well, would be great if we can >> update the RC with new vdsm soon after. >> > >> > Thanks, >> > michal >> > >> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1524119 >> > >> > We have right now 3 blockers: >> > ID▲ oVirt Team Product▲ Component▲ Assignee >> Status▼ Summary Severity Priority▲ >> > 1522641 Node cockpit-ovirt Hosted Engine >> phbailey(a)redhat.com NEW Hosted Engine deployment failed, there >> display 'Timed out... urgent unspecified >> >> seems this still requires clarification. There is some misunderstanding >> between the assignee and qe. >> > On my opinion it's just a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1512534 and today Nikolai got it again on RHEL with everything at latest version. It's not 100% reproducible being a time based issue.

>> > 1525353 Network ovirt-engine BLL.Network >> eraviv(a)redhat.com NEW vNIC mapping is broken on import from >> data domain - vNICs... urgent urgent >> >> Dan, can you update why this is a urgent/urgent blocker? It doesn’t >> seem to qualify for that severity. Import VM from SD and end up with empty >> mapping you can easily fix…that hardly critically affects running workloads. >> > > VDSM build is ready and added to ovirt-4.2-pre repo. > Pending decision on cockpit-ovirt and ovirt-engine for going ahead with > the release. > > > > > >> >> > 1524119 Virt vdsm General fromani(a)redhat.com POST >> Failed to migrate HE VM urgent urgent >> > >> > >> > Looks like we'll need a RC3. >> > >> > >> > >> > >> >> On 12 Dec 2017, at 16:45, Sandro Bonazzola <sbonazzo(a)redhat.com&gt; >> wrote: >> >> >> >> The oVirt Project is pleased to announce the availability of the >> Second Candidate Release of oVirt 4.2.0, as of December 12th, 2017 >> >> >> >> This is pre-release software. This pre-release should not to be used >> in production. >> >> Please take a look at our community page[1] to learn how to ask >> questions and interact with developers and users. >> >> All issues or bugs should be reported via oVirt Bugzilla[2]. >> >> >> >> This update is the second candidate release of the 4.2.0 version. >> This release brings more than 280 enhancements and more than one thousand >> bug fixes, including more than 500 high or urgent severity fixes, on top of >> oVirt 4.1 series. >> >> >> >> What's new in oVirt 4.2.0? >> >> >> >> • The Administration Portal has been completely redesigned using >> Patternfly, a widely adopted standard in web application design. It now >> features a cleaner, more intuitive design, for an improved user experience. >> >> • There is an all-new VM Portal for non-admin users. >> >> • A new High Performance virtual machine type has been added to >> the New VM dialog box in the Administration Portal. >> >> • Open Virtual Network (OVN) adds support for Open vSwitch >> software defined networking (SDN). >> >> • oVirt now supports Nvidia vGPU. >> >> • The ovirt-ansible-roles package helps users with common >> administration tasks. >> >> • Virt-v2v now supports Debian/Ubuntu based VMs. >> >> >> >> For more information about these and other features, check out the >> oVirt 4.2.0 blog post. >> >> >> >> This release is available now on x86_64 architecture for: >> >> * Red Hat Enterprise Linux 7.4 or later >> >> * CentOS Linux (or similar) 7.4 or later >> >> >> >> This release supports Hypervisor Hosts on x86_64 and ppc64le >> architectures for: >> >> * Red Hat Enterprise Linux 7.4 or later >> >> * CentOS Linux (or similar) 7.4 or later >> >> * oVirt Node 4.2 (available for x86_64 only) >> >> >> >> See the release notes draft [3] for installation / upgrade >> instructions and a list of new features and bugs fixed. >> >> >> >> Notes: >> >> - oVirt Appliance is already available. >> >> - oVirt Node is already available [4] >> >> >> >> Additional Resources: >> >> * Read more about the oVirt 4.2.0 release highlights: >> http://www.ovirt.org/release/4.2.0/ >> >> * Get more oVirt project updates on Twitter: >> https://twitter.com/ovirt >> >> * Check out the latest project news on the oVirt blog: >> http://www.ovirt.org/blog/ >> >> >> >> [1] https://www.ovirt.org/community/ >> >> [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt >> >> [3] http://www.ovirt.org/release/4.2.0/ >> >> [4] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ >> >> >> >> -- >> >> SANDRO BONAZZOLA >> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >> >> Red Hat EMEA >> >> >> >> TRIED. TESTED. TRUSTED. >> >> >> >> _______________________________________________ >> >> Devel mailing list >> >> Devel(a)ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/devel >> > >> > >> > >> > >> > -- >> > SANDRO BONAZZOLA >> > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >> > Red Hat EMEA >> > >> > TRIED. TESTED. TRUSTED. >> > >> >> > > > -- > > SANDRO BONAZZOLA > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel >