[Users] [ANN] oVirt 3.4.0 beta2 is now available

[Markus Stockhausen]

> Von: users-bounces at ovirt.org [users-bounces at ovirt.org]" im Auftrag von "Sandro Bonazzola [sbonazzo at redhat.com]
> Gesendet: Freitag, 7. Februar 2014 11:36
> An: announce at ovirt.org; Users at ovirt.org; engine-devel; arch; VDSM Project Development
> Betreff: [Users] [ANN] oVirt 3.4.0 beta2 is now available
> 
> The oVirt team is pleased to announce that the 3.4.0 second beta release is now available for testing.
> 
> Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1].
> Please ensure to follow install instruction from release notes if you're going to test it.
> The existing repository ovirt-3.4.0-prerelease has been updated for delivering this beta and future refreshes until release candidate.
> 
> A new oVirt Node build will be available soon as well.
> 
> You're welcome to join us testing this beta release in next week test day [2] scheduled for 2014-02-11!
> 
> 
> [1] http://www.ovirt.org/OVirt_3.4.0_release_notes
> [2] http://www.ovirt.org/OVirt_3.4_Test_Day
> 
> --
> Sandro Bonazzola

Hello Sandro,

may I politely ask to set BZ 1062615 for target release 3.4.0 - and as a blocker too?
Dan's information suggest that it is still existent in 3.4.0 beta2. Maybe someone can
proove it in a beta environment too and update the bug.

It seems as if Ovirt does not remember timezone/clock settings of a Windows VM.
As a side effect a VM may always come up with a predefined time gap until the
the ntp client wil fix the time. If that gap is too large we could suffer from some
unwanted side effects

- ntp time sync may not work because of too high gap
- kerberos authentication may fail because of too high gap

Markus
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140207/a27db902/attachment-0001.txt>