Created attachment 1680645 [details] Includes image of the error, logs of the engine/vdsm and QEMU Description of problem: When I try to access a VM's console (Any type of console VNC/Spice/NoVNC...) I see the error "Sorry, VM Portal is currently having some issues." instead of downloading a .vv file or a webpage for the noVNC. Version-Release number of selected component (if applicable): RHEV 4.4.0-31. RHEL 8.2 Both Hosts and Engine RHEVM: org.ovirt.engine-root-4.4.0-33 VDSM: vdsm-4.30.44-1.el7ev How reproducible: 100% Steps to Reproduce: 1. Enter VM portal 2. Run a VM 3. Open the VM's console in any method (SPICE/VNC/noVNC...) Actual results: I get this text instead of the console's file/webpage: "Sorry, VM Portal is currently having some issues." I get errors in the web console: -"Uncaught saga error (store.js): TypeError: (0 , g.setVmSessions) is not a function" -"TypeError: (0 , g.setVmSessions) is not a function" Expected results: Enter console's noVNC webpage or download .vv file for virt viewer for any other console type. Additional info:
Here's the patch for fixing the VNC Browser console issue: https://gerrit.ovirt.org/#/c/109214/
Checked on RHV 4.4.1-3 with RHEL 8.2 engine and hosts. Steps: 1. Create a 4.4 data center and cluster, add a host and add a data storage. 2. Create a VM. 3. Login to the VM portal. 4. Access the VM's console (using VNC/Spice/noVNC). Actual: 1-3 steps were executed successfully. 4. I successfully launched and downloaded the vv files for the VNC and SPICE (In both the Admin Portal and the VM portal) But in the VM portal I wasn't able to launch the noVNC console of the same VM while in the Admin Portal I successfully launched it (same VM, noVNC). Expected: 4. All the VM consoles to be accessible and working correctly. I attached browser's console log in attachments and engine.log. I think this problem is connected to this bug, so I will move the status to assigned.
I verified it again on RHV 4.4.1-4 and everything works correctly.
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.