Console of instances is not available

Bug #1822212 reported by Juan Carlos Alonso
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
High
Teresa Ho

Bug Description

Title
-----
Consoles of instances (VM) is not available through Horizon.

Brief Description
-----------------
Console is not available for active VMs in Horizon.

Severity
--------
<Critical: Feature is not usable after the defect>

Steps to Reproduce
------------------
- Launch an instance
- Go to Horizon -> Project -> Compute -> Instancess -> VM -> Console

Expected Behavior
------------------
Console of VM can be used

Actual Behavior
----------------
Console is not available

Reproducibility
---------------
<Reproducible/100%>

System Configuration
--------------------
All

Branch/Pull Time/Commit
-----------------------
cengn iso: 20190328

tags: added: stx.containers
Ghada Khalil (gkhalil)
description: updated
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as release gating; high priority given issue is seen in sanity

Changed in starlingx:
assignee: nobody → Teresa Ho (teresaho)
importance: Undecided → High
status: New → Triaged
tags: added: stx.2019.05
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to stx-config (master)

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

Changed in starlingx:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to stx-config (master)

Reviewed: https://review.openstack.org/649307
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=9e486fd590c83749b61d9c031e3ca4d067cbc0bc
Submitter: Zuul
Branch: master

commit 9e486fd590c83749b61d9c031e3ca4d067cbc0bc
Author: Teresa Ho <email address hidden>
Date: Mon Apr 1 22:13:20 2019 -0400

    Remove ingress http port helm override

    Previously, the http port for kube-system ingress was set to 8081 in
    the helm override due to conflicts with port 80 and 8080 when the oam
    floating IP was used.
    Since the default local domain or a configured FQDN is now used to
    connect to horizon and novncproxy, the http port for ingress needs
    to be set back to the default port 80 for http.

    Closes-bug: 1822212

    Change-Id: I253ea54294703f74b042202bf444863f3a888cf0
    Signed-off-by: Teresa Ho <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
Ken Young (kenyis)
tags: added: stx.2.0
removed: stx.2019.05
Revision history for this message
Erich Cordoba (ericho) wrote :

This is still an issue. I can't reach the console on this url (see attached image)

http://novncproxy.openstack.svc.cluster.local/vnc_auto.html?token=3b216d51-a165-4403-bcbd-ee89d733aac8&title=Testing+STX(7be4d56c-850d-4567-98df-099ab4985549

I'm running a simplex configuration in a VM, so I don't have a DNS that can resolve "novncproxy.openstack.svc.cluster.local" if I open horizon in my host's browser.

If I try to reach the following URL, doesn't work neither.

http://10.10.10.3:6080/vnc_auto.html?token=3b216d51-a165-4403-bcbd-ee89d733aac8&title=Testing+STX(7be4d56c-850d-4567-98df-099ab4985549

However, I if create a SSH tunnel to expose the 6080 port then I can see the VNC console.

ssh -L 6080:localhost:6080 wrsroot@10.10.10.3

Revision history for this message
Erich Cordoba (ericho) wrote :

Screenshot of instance's console non reachable.

Revision history for this message
Teresa Ho (teresaho) wrote :
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.