Description of problem:
The latest version upstream of noVNC is 0.5.1. The current version in OSP, 0.4, is quite old at this point, and lacks several important bug fixes.
Additionally, as of 15-Mar-2015, the official CentOS 7 update repositories are pushing novnc.noarch 0.5.1-2.el7 update out to CentOS 7 servers. So after I ran a "yum update" on my oVirt self-hosted engine running CentOS 7 yesterday (on 15-Mar), I got errors when trying to launch the noVNC console for any of VMs.
Version-Release number of selected component (if applicable):
novnc.noarch 0.5.1-2.el7 on CentOS/RHEL 7
Always as of 15-Mar-2015 when the upstream CentOS yum update repositories starting pushing noVNC 0.5.1.
Steps to Reproduce:
1. Do a yum update to your CentOS 7.0 oVirt engine which should pull down the latest novnc 0.5.1 package.
2. Try to open a noVNC console to any VM running on your oVirt engine.
noVNC console should render.
For now, I downloaded novnc-0.4-7.el7.noarch rpm and downgraded to the version that works with this command: rpm -Uvh --oldpackage novnc-0.4-7.el7.noarch.rpm.
This workaround seems necessary until oVirt webadmin code is updated to accomodate noVNC 0.5.1.
Michal, noVNC is causing a (minor?) regression here, I suggest to re-target this to 3.5.4.
Might be easier to push Conflicts: then
Fix won't happen any time soon, well, at least couple of weeks
Confirming the issue...
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
ok, novnc works
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.