In GWT 2.5, there are stricter requirements for classes that are being (de)serialized via the GWT RPC (de)serialization mechanism: a. class should have no member initialization (members should be initialized only within methods, typically c'tors) b. class should have an explicit default c'tor. need to change the relevant classes to comply with these requirements. 'b' is already taken care of by these patches [1] still need to apply 'a' as well. [1] by amureini: http://gerrit.ovirt.org/#/c/18133/ http://gerrit.ovirt.org/#/c/18139/ http://gerrit.ovirt.org/#/c/18134/ http://gerrit.ovirt.org/#/c/18140/ http://gerrit.ovirt.org/#/c/18132/ http://gerrit.ovirt.org/#/c/18135/ http://gerrit.ovirt.org/#/c/18138/ http://gerrit.ovirt.org/#/c/18137/
(In reply to Einav Cohen from comment #0) > > 'b' is already taken care of by these patches [1] > still need to apply 'a' as well. correction: should be the other way around: 'a' (no member init) is already taken care of. still need to apply 'b' (explicit default c'tor).
(In reply to Einav Cohen from comment #1) > (In reply to Einav Cohen from comment #0) > > > > 'b' is already taken care of by these patches [1] > > still need to apply 'a' as well. > > correction: should be the other way around: > 'a' (no member init) is already taken care of. > still need to apply 'b' (explicit default c'tor). No-argument constructor check is implemented in patch http://gerrit.ovirt.org/#/c/20274/
Patch http://gerrit.ovirt.org/#/c/20274/ updated and ready for review. Once merged into master, all relevant patches will be backported and BZ will be moved to MODIFIED.
rc build done, moving to ON_QA, packages will be available on updates-testing repository.
oVirt 3.3.2 has been released resolving the problem described in this bug report.