Description of problem: After an undetermined amount of time, the "Enable WAN Options" setting and checkbox were missing from the UserPortal's Spice Console Options dialog box. Only a restart of the ovirt-engine service caused this to re-appear. Version-Release number of selected component (if applicable): 3.1.0-50 How reproducible: Intermittent Steps to Reproduce: Unknown. The customer noticed it was missing one day. Expected results: "Enable WAN Options" should always be visible Additional Info: A "service ovirt-engine restart" made the option re-appear in the UserPortal. No logs are available from the incident because the customer does not know when the problem began.
might be the same as recent issues with Guest Agent socket connection. Vinzenz, can you verify?
What I can say is that this _can_ only be related to the guest agent socket problems IF vdsm would have been restarted. However since it was the ovirt-engine service which solved the issue it is not related to that. Therefore this should be assigned back to some component of the engine
without logs we can't tell anything more. Option's visibility depends on browser and application list supplied by Guest Agent. Next time it would be great to test whether there are any issues at vdsm level, i.e. whether VDSM is able to get the application list from Guest Agent and there is no issue with communication between VDSM and Engine
(In reply to Michal Skrivanek from comment #4) > without logs we can't tell anything more. Option's visibility depends on > browser and application list supplied by Guest Agent. > > Next time it would be great to test whether there are any issues at vdsm > level, i.e. whether VDSM is able to get the application list from Guest > Agent and there is no issue with communication between VDSM and Engine There is definitely some sort of issue at the vdsm level. My customer was in a hurry to get things back up and running today so they could continue testing, so we didn't try to get the application list but, I filed bug#967136 just now to tie all 3 issues we've seen with vdsm together. We have logs in that BZ as well.