← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #94411

[Bug 2076440] [NEW] noVNC instance console fails with "Something went wrong, connection is closed"

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

Description
===========
noVNC instance console cannot be accessed via Horizon Dashboard or via direct
link, and it fails with "Something went wrong, connection is closed" error.

Steps to reproduce
==================
1. Create a VM
    openstack server create test-vm --image cirros --key-name default \
        --flavor m1.nano --network EXTERNAL_NETWORK
2. Get a console url
    openstack console url show test-vm
3. Use the link to access noVNC console in a web browser

Expected result
===============
noVNC console works, VM can be accessed and interacted through the console.

Actual result
=============
noVNC console displays in the top bar:
1. Loading
2. Connecting
3. Something went wrong, connection is closed

Environment
===========
OpenStack RDO Wallaby on RHEL 9.4
Nova containers running on Rocky Linux 9.3 and Python3.9

python3-novaclient-17.4.1-0.20220916102938.5ee4427.el9.noarch
python3-nova-23.2.3-0.20231017155403.2ace99d.el9.noarch
openstack-nova-common-23.2.3-0.20231017155403.2ace99d.el9.noarch
openstack-nova-novncproxy-23.2.3-0.20231017155403.2ace99d.el9.noarch

Logs & Configs
==============
nova-novncproxy.log:
2024-08-09 16:52:17.824 2 INFO nova.console.websocketproxy [-] WebSocket server settings:
2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - Listen on 172.17.1.243:6080
2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - Web server (no directory listings). Web root: /usr/share/novnc
2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - No SSL/TLS support (no cert file)
2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - proxying from 172.17.1.243:6080 to None:None
2024-08-09 16:52:43.435 32 INFO nova.console.websocketproxy [-] 172.17.1.243 - - [09/Aug/2024 16:52:43] 172.17.1.243: Plain non-SSL (ws://) WebSocket connection
2024-08-09 16:52:43.436 32 INFO nova.console.websocketproxy [-] 172.17.1.243 - - [09/Aug/2024 16:52:43] 172.17.1.243: Path: '/?token=00467fbe-6123-4c55-bc4c-4e6fa320f3ac'
2024-08-09 16:52:43.582 32 WARNING oslo_config.cfg [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -] Deprecated: Option "heartbeat_in_pthread" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
2024-08-09 16:52:43.614 32 INFO nova.console.websocketproxy [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -]   2: connect info: ConsoleAuthToken(access_url_base='https://(OBFUSCATED):13080/vnc_auto.html',console_type='novnc',created_at=2024-08-09T14:52:42Z,host='172.17.1.187',id=2,instance_uuid=53f0efa0-2f10-49ad-ab17-3765e2381cf6,internal_access_path=None,port=5900,token='***',updated_at=None)
2024-08-09 16:52:43.614 32 INFO nova.console.websocketproxy [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -]   2: connecting to: 172.17.1.187:5900
2024-08-09 16:52:43.659 32 INFO nova.console.websocketproxy [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -] handler exception: 'array.array' object has no attribute 'fromstring'


nova.conf on the controller:
...
[vnc]
novncproxy_host=172.17.1.243
novncproxy_port=6080
auth_schemes=none


nova.conf on the compute hosting the VM:
...
[vnc]
enabled=True
server_listen=0.0.0.0
server_proxyclient_address=172.17.1.187
novncproxy_base_url=https://(OBFUSCATED):13080/vnc_auto.html

** Affects: nova
     Importance: Undecided
         Status: In Progress

** Attachment added: "Screenshot of noVNC console failure"
   https://bugs.launchpad.net/bugs/2076440/+attachment/5804124/+files/noVNC-Console-Failure-screenshot.png

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2076440

Title:
  noVNC instance console fails with "Something went wrong, connection is
  closed"

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Description
  ===========
  noVNC instance console cannot be accessed via Horizon Dashboard or via direct
  link, and it fails with "Something went wrong, connection is closed" error.

  Steps to reproduce
  ==================
  1. Create a VM
      openstack server create test-vm --image cirros --key-name default \
          --flavor m1.nano --network EXTERNAL_NETWORK
  2. Get a console url
      openstack console url show test-vm
  3. Use the link to access noVNC console in a web browser

  Expected result
  ===============
  noVNC console works, VM can be accessed and interacted through the console.

  Actual result
  =============
  noVNC console displays in the top bar:
  1. Loading
  2. Connecting
  3. Something went wrong, connection is closed

  Environment
  ===========
  OpenStack RDO Wallaby on RHEL 9.4
  Nova containers running on Rocky Linux 9.3 and Python3.9

  python3-novaclient-17.4.1-0.20220916102938.5ee4427.el9.noarch
  python3-nova-23.2.3-0.20231017155403.2ace99d.el9.noarch
  openstack-nova-common-23.2.3-0.20231017155403.2ace99d.el9.noarch
  openstack-nova-novncproxy-23.2.3-0.20231017155403.2ace99d.el9.noarch

  Logs & Configs
  ==============
  nova-novncproxy.log:
  2024-08-09 16:52:17.824 2 INFO nova.console.websocketproxy [-] WebSocket server settings:
  2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - Listen on 172.17.1.243:6080
  2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - Web server (no directory listings). Web root: /usr/share/novnc
  2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - No SSL/TLS support (no cert file)
  2024-08-09 16:52:17.825 2 INFO nova.console.websocketproxy [-]   - proxying from 172.17.1.243:6080 to None:None
  2024-08-09 16:52:43.435 32 INFO nova.console.websocketproxy [-] 172.17.1.243 - - [09/Aug/2024 16:52:43] 172.17.1.243: Plain non-SSL (ws://) WebSocket connection
  2024-08-09 16:52:43.436 32 INFO nova.console.websocketproxy [-] 172.17.1.243 - - [09/Aug/2024 16:52:43] 172.17.1.243: Path: '/?token=00467fbe-6123-4c55-bc4c-4e6fa320f3ac'
  2024-08-09 16:52:43.582 32 WARNING oslo_config.cfg [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -] Deprecated: Option "heartbeat_in_pthread" from group "oslo_messaging_rabbit" is deprecated for removal.  Its value may be silently ignored in the future.
  2024-08-09 16:52:43.614 32 INFO nova.console.websocketproxy [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -]   2: connect info: ConsoleAuthToken(access_url_base='https://(OBFUSCATED):13080/vnc_auto.html',console_type='novnc',created_at=2024-08-09T14:52:42Z,host='172.17.1.187',id=2,instance_uuid=53f0efa0-2f10-49ad-ab17-3765e2381cf6,internal_access_path=None,port=5900,token='***',updated_at=None)
  2024-08-09 16:52:43.614 32 INFO nova.console.websocketproxy [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -]   2: connecting to: 172.17.1.187:5900
  2024-08-09 16:52:43.659 32 INFO nova.console.websocketproxy [req-399ddc1f-ef74-4772-af5c-00b29cc2036a - - - - -] handler exception: 'array.array' object has no attribute 'fromstring'

  
  nova.conf on the controller:
  ...
  [vnc]
  novncproxy_host=172.17.1.243
  novncproxy_port=6080
  auth_schemes=none

  
  nova.conf on the compute hosting the VM:
  ...
  [vnc]
  enabled=True
  server_listen=0.0.0.0
  server_proxyclient_address=172.17.1.187
  novncproxy_base_url=https://(OBFUSCATED):13080/vnc_auto.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2076440/+subscriptions
  Thread Previous • Date Previous • • Thread Next