novncproxy in Newton uses outdated novnc 0.5 which breaks Nova noVNC consoles
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Matt Riedemann | ||
tripleo |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
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:/
https:/
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.
tags: | added: console openstack-version.newton |
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → 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.