novncproxy in Newton uses outdated novnc 0.5 which breaks Nova noVNC consoles

[Felipe Alfaro Solana]

Delorean Newton (CentOS 7) ships with noVNC 0.5.2 in the Overcloud images. Even building an Overcloud image (DIB) produces an image with noVNC 0.5.2. The problem seems to be that CentOS 7 does not ship anything newer than 0.5.2. However, Red Hat Enterprise Linux 7 does indeed ship noVNC 0.6.

In any case, Nova noVNC consoles in Newton don't work with noVNC 0.5.2. My workaround was to customize the Overcloud base image and replace the 0.5.2 RPM with a 0.6.2 RPM that I downloaded from some CentOS CI repository.

Steps to reproduce
==================

Follow instructions from https://docs.openstack.org/tripleo-docs/latest/install/installation/installing.html to install an OpenStack Undercloud using Newton, and either download the Overcloud base images from here
https://images.rdoproject.org/newton/delorean/consistent/testing/ or build them yourself directly from the Undercloud.

In any case, the Overcloud base image ships with noVNC 0.5.2-1 instead of 0.6.*.

Expected result
===============

A newer version of noVNC that does not break the Nova noVNC console.

[Matt Riedemann (mriedem)]

This doesn't seem like anything that nova itself can control, I don't know if this is something that goes to RDO or tripleo or we just close.

[Matt Riedemann (mriedem)]

One could argue I guess that we could mention something in this guide saying that noVNC versions < 0.6 are known to be problematic?

https://docs.openstack.org/nova/latest/admin/remote-console-access.html#nova-novncproxy-novnc

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/562847

[Matt Riedemann (mriedem)]

Docs patch: https://review.openstack.org/#/c/562847/

[melanie witt (melwitt)]

I wish this bug report included a paste for the encountered error. It's probably unlikely there's anything we could do in nova to avoid this but it would be nice to know what is failing and why version >= 0.6 is required. So far, I don't find any mention about it in the code.

[Alex Schultz (alex-schultz)]

From a tripleo standpoint, it's a packaging issue in RDO. Additionally newton is basically EOL so closing that out as won't fix.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/562847
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7c37aba40b908c18aafaf8df7849d1f074c3098d
Submitter: Zuul
Branch: master

commit 7c37aba40b908c18aafaf8df7849d1f074c3098d
Author: Matt Riedemann <email address hidden>
Date: Thu Apr 19 18:00:06 2018 -0400

    Mention that users need noVNC >= 0.6

    Apparently versions below 0.6 don't work with
    the nova-novncproxy service.

    Change-Id: I9f355f2af7b90022b01ad0bfbe7081d73dcc1416
    Closes-Bug: #1752896

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.