[ovirt-users] Re: [ovirt-devel] Re: oVirt 4.4.0 Beta release refresh is now available for testing

On Fri, Apr 17, 2020 at 6:40 PM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > oVirt 4.4.0 Beta release refresh is now available for testing > > The oVirt Project is excited to announce the availability of the beta > release of oVirt 4.4.0 refresh (beta 4) for testing, as of April 17th, 2020 > > This release unleashes an altogether more powerful and flexible open > source virtualization solution that encompasses hundreds of individual > changes and a wide range of enhancements across the engine, storage, > network, user interface, and analytics on top of oVirt 4.3. > > > Hello, I have tried the iso of ovirt node ng to configure a single host HCI environment. Using the wizard for single node, at the beginning in the window where you have to insert the fqdn of the storage node I see a javascript exception (a red Ooops! in top right of cockpit page tells me that). Both on Google Chrome and in firefox. In practice you cannot type anything and in js console of chrome I see: app.js:43 Uncaught TypeError: Cannot read property 'checked' of null at n.value (app.js:43) at changeCallBack (app.js:43) at Object.b (app.js:27) at w (app.js:27) at app.js:27 at S (app.js:27) at T (app.js:27) at Array.forEach (<anonymous>) at _ (app.js:27) at N (app.js:27) We have patch available and the respective BZ is

Sort of workaround is to type a character (you don't see anything), then click the ipv6 related checkbox just above the input line, and then you see the first character, then again, alternating the checkbox and a character.... you see every time appear the new character typed. You cannot type the full fqdn in one flow because only the last character appears then when you click on the checkbox... This anyway let me continue and type the whole storage hostname and go ahead with the installation. I arrive up to the final step "Finish Deployment", but when the host exits final global maintenance and the engine VM starts, it goes into panic and I realized that I missed the pass-through cpu flag for the hypervisor vm, so I'm going to retry. In the mean time can anyone verify the javascript exception above? Gianluca _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org 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/devel@ovirt.org/message/IKBLU764LCR...