Protocols for websocket should not be hardcorded

Bug #1698092 reported by Shu Muto
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Shu Muto
Zun UI
Fix Released
Medium
Shu Muto

Bug Description

To use serial console with any websocket protocol, the protocols should not be hardcoded.

Shu Muto (shu-mutou)
Changed in horizon:
assignee: nobody → Shu Muto (shu-mutou)
Shu Muto (shu-mutou)
Changed in zun-ui:
assignee: nobody → Shu Muto (shu-mutou)
status: New → In Progress
Changed in horizon:
status: New → In Progress
Changed in zun-ui:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

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

Akihiro Motoki (amotoki)
Changed in horizon:
milestone: none → pike-3
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/474520
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4493b6f75ff40c7f12f2bd0b4305bc2562b468a6
Submitter: Jenkins
Branch: master

commit 4493b6f75ff40c7f12f2bd0b4305bc2562b468a6
Author: Shu Muto <email address hidden>
Date: Thu Jun 15 18:06:47 2017 +0900

    Enable to set protocols of WebSocket for serial console

    This patch enables to set protocols of WebSocket for serial console.
    Also, this enables to use serial console not only from instance
    but also plugins.
    e.g. Zun UI can access container console provided by docker.

    Change-Id: Ib0df9ddfc74f98bfea75abce3b5d5479e3cd47bd
    Needed-By: I41f236f2762613e56748bb05eb7ce0e4c26158d2
    Closes-Bug: #1698092

Changed in horizon:
status: In Progress → Fix Released
Shu Muto (shu-mutou)
Changed in zun-ui:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 12.0.0.0b3

This issue was fixed in the openstack/horizon 12.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.