Red Hat Bugzilla – Bug 988021
CD images not displayed / GWT RPC Serizalization issue
Last modified: 2015-05-04 21:43:41 EDT
Description of problem:
CD images that exist in ISO domain don't appear in the attach CD to VM list box.
Version-Release number of selected component (if applicable):
Always (for me).
Steps to Reproduce:
1. Create ISO domain.
2. Add CD image there.
3. Create a VM.
The attach CD list box is empty.
There should be an option to pick the CD image that exists in the domain.
The engine log doesn't display any error. On the contrary, a log message is displayed that shows that the CD image is actually retrieved by vdsbroker and irsbroker, and just isn't displayed in the UI.
it seems to work, did you create/open the VM while the iso already existed on iso domain? The attach CD you mean in spice client or in user portal?
I created the VM before the ISO existed on the domain, but obviously tried to attach the ISO to the CD drive of the VM after I put it in the domain (manually, not via image-uploader). By "attaching" I mean in either the Edit VM dialog or the Run Once dialog, both in the webadmin portal. The refresh button didn't help either. I have heard suggestions that this might have been due to the GWT upgrade.
per Vojtech this is a general GWT RPC serialization issue, assigning to him
*** Bug 988407 has been marked as a duplicate of this bug. ***
*** Bug 988751 has been marked as a duplicate of this bug. ***
vojtech - fixed by now?
workaround solution merged to master:
Einav, do want to track it for another fix or is this good enough?
(In reply to Lior Vernia from comment #0)
> The engine log doesn't display any error. On the contrary, a log message is
> displayed that shows that the CD image is actually retrieved by vdsbroker
> and irsbroker, and just isn't displayed in the UI.
The error was in server.log - GWT RPC servlet (WebModePayloadSink:636) failed while attempting to serialize RepoImage business entity to be passed back to WebAdmin.
(In reply to Itamar Heim from comment #6)
> vojtech - fixed by now?
Yes, this issue is already fixed.
Juan's initial solution [http://gerrit.ovirt.org/#/c/17330/] was later reverted [http://gerrit.ovirt.org/#/c/17349/] because we found the root cause and fixed RepoImage entity itself [http://gerrit.ovirt.org/#/c/17352/].
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)