Description of problem: Certain builds displayed a server error 500 originally when entering the Import functionality within the VM screen. The screen shot shows the error: https://imgur.com/a/AadtU1u Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Enter the Compute -> Virtual Machines screen 2. Press the More button and choose Import 3. The dialog appeared Actual results: We received a dialog with the error. Expected results: We would enter the Import screen Additional info: This issue seemed to change with each re-base / patch until finally it stopped occurring.
Following exception is thrown in server.log: Caused by: com.google.gwt.user.client.rpc.SerializationException: Type 'java.util.RegularEnumSet' was not included in the set of types which can be serialized by this SerializationPolicy or its Class object could not be loaded. For security purposes, this type will not be serialized.: instance = [V1, V2, V3, V4]
Is 4.3.3 not affected? If it is, isn’t it always reproducible? If it is, shouldn’t it be a blocker?
Hi Martin, I tried to reproduce in both 4.3.3.3 and 4.3.3.2 engines with chrome(Version 70.0.3538.77 (Official Build) (64-bit)) and firefox(63.0 (64-bit)) browsers and this did not reproduce even once. What am I missing here? We should be able to reproduce easily to verify when the fix is available.
(In reply to Avihai from comment #4) > Hi Martin, > > I tried to reproduce in both 4.3.3.3 and 4.3.3.2 engines with chrome(Version > 70.0.3538.77 (Official Build) (64-bit)) and firefox(63.0 (64-bit)) browsers > and this did not reproduce even once. with older <4.3.2 hosts?
This is virt bug, moving QA contact to Meital.
No longer reproducible, and the attached patch should prevent future occurences. CLOSE - WORKSFORME?
So again, it should reproduce with: 4.3.3.2 - 4.3.3.4 engine + any 4.2 or older host
I do not have env's available with this engine-host combo. Peter, can you help with this, please?
I tested with engine 4.3.3.3-0.1.el7 (4.3.3-3) and host with vdsm-4.20.48-1.el7ev.x86_64 (4.2.8-10) and I didn't reproduce this issue Note that I used fresh installed engine and host (I didn't do upgrade) Should I test also upgrade from 4.2.8 to 4.3.3 and check the import dialog when the hosts are not upgraded?
no, that's the correct version set. Any other condition required in your opinion, Martin?
(In reply to Michal Skrivanek from comment #24) > no, that's the correct version set. Any other condition required in your > opinion, Martin? Seems OK to me
Not reproducible (tested scenario with 4.2.8 hosts), working also after patch. If you reproduce this issue, please provide exact steps and logs. Verified in version: ovirt-engine-4.3.3.6-0.1.el7.noarch