vm console showing blank screen

Bug #1590250 reported by rohit
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
High
Unassigned

Bug Description

Hi,
I installed openstack using devstack on new ubuntu machine, it installed properly, and VM also instantiated successfully, but when I try to access console of VM instance, it is simply showing blank screen..
I checked novnc server , it is working and receiving requests.
I am running followsing services :-

disable_service n-net
enable_service neutron q-svc q-agt q-dhcp q-l3 q-meta
disable_service n-spice
enable_service n-novnc
disable_service n-xvnc
enable_service n-sproxy
disable_service tempest

this problem is coming on liberty as well as on mitaka.

could this problem relates to system hardware also?

Tags: console
tags: added: console
Revision history for this message
Takashi Natsume (natsume-takashi) wrote :

Need more information.

* Log messages (log files) of nova-novncproxy

Changed in nova:
status: New → Incomplete
Revision history for this message
rohit (rohit121003) wrote :

Hi,
Please find n-novnc logs.

2016-06-08 19:13:54.587 28590 DEBUG nova.console.websocketproxy [-] Reaping zombies, active child count is 4 vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:860
2016-06-08 19:13:54.589 28590 DEBUG nova.console.websocketproxy [-] Reaping zombies, active child count is 1 vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:860
2016-06-08 19:15:01.578 28590 DEBUG nova.console.websocketproxy [-] Reaping zombies, active child count is 0 vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:860
2016-06-08 19:15:10.273 28590 DEBUG nova.console.websocketproxy [-] 192.168.0.4: new handler Process vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:860
192.168.0.4 - - [08/Jun/2016 19:15:10] "GET /vnc_auto.html?token=470344dd-cc61-442b-bbc9-fa70a09e6249&title=vm1(d6c2d016-a12b-4240-b253-1c5bd08148c7) HTTP/1.1" 200 -
2016-06-08 19:15:10.537 28590 DEBUG nova.console.websocketproxy [-] 192.168.0.4: new handler Process vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:860
192.168.0.4 - - [08/Jun/2016 19:15:10] "GET /websockify?token=470344dd-cc61-442b-bbc9-fa70a09e6249 HTTP/1.1" 101 -
192.168.0.4 - - [08/Jun/2016 19:15:10] 192.168.0.4: Plain non-SSL (ws://) WebSocket connection
192.168.0.4 - - [08/Jun/2016 19:15:10] 192.168.0.4: Version hybi-13, base64: 'False'
192.168.0.4 - - [08/Jun/2016 19:15:10] 192.168.0.4: Path: '/websockify?token=470344dd-cc61-442b-bbc9-fa70a09e6249'
2016-06-08 19:15:10.546 INFO oslo.messaging._drivers.impl_rabbit [req-72d83451-6ec0-4fb4-82e2-b8959afbe98c None None] Connecting to AMQP server on 192.168.0.4:5672
2016-06-08 19:15:10.557 INFO oslo.messaging._drivers.impl_rabbit [req-72d83451-6ec0-4fb4-82e2-b8959afbe98c None None] Connected to AMQP server on 192.168.0.4:5672
2016-06-08 19:15:10.563 INFO oslo.messaging._drivers.impl_rabbit [req-72d83451-6ec0-4fb4-82e2-b8959afbe98c None None] Connecting to AMQP server on 192.168.0.4:5672
2016-06-08 19:15:10.578 INFO oslo.messaging._drivers.impl_rabbit [req-72d83451-6ec0-4fb4-82e2-b8959afbe98c None None] Connected to AMQP server on 192.168.0.4:5672
2016-06-08 19:15:10.645 INFO nova.console.websocketproxy [req-72d83451-6ec0-4fb4-82e2-b8959afbe98c None None] 21: connect info: {u'instance_uuid': u'd6c2d016-a12b-4240-b253-1c5bd08148c7', u'internal_access_path': None, u'last_activity_at': 1465393509.788952, u'console_type': u'novnc', u'host': u'127.0.0.1', u'token': u'470344dd-cc61-442b-bbc9-fa70a09e6249', u'access_url': u'http://192.168.0.4:6080/vnc_auto.html?token=470344dd-cc61-442b-bbc9-fa70a09e6249', u'port': u'5900'}
2016-06-08 19:15:10.646 INFO nova.console.websocketproxy [req-72d83451-6ec0-4fb4-82e2-b8959afbe98c None None] 21: connecting to: 127.0.0.1:5900
{<}>{<}>{<}>{<}>{<}>{<}>{<}>{<}>{<}>

Changed in nova:
status: Incomplete → Confirmed
Changed in nova:
importance: Undecided → High
Revision history for this message
Jian Wen (wenjianhn) wrote :

I failed to reproduce the bug.

I am using RDO with an all in one installation.
https://www.rdoproject.org/install/quickstart/

Revision history for this message
Qijing Li (qijing-lee) wrote :

This bug did not happen on my devstack on ubuntu.

Here is my local.conf

 # Do not use Nova-Network
 disable_service n-net
 # Enable Neutron
 ENABLED_SERVICES+=,q-svc,q-dhcp,q-meta,q-agt,q-l3

Revision history for this message
rohit (rohit121003) wrote :

Hi,
my os is ubuntu 16 .10 (xenial), is it related with some specific OS version?
I will try with other OS.

Revision history for this message
Maciej Szankin (mszankin) wrote :

Tested current master branch on 16.04 with local.conf just as in bug description and everything works correctly.

Are you sure that console is available on the same IP as the VM? And if not, that this IP is ping-able?

Marking as invalid until any further proof appears.

Changed in nova:
status: Confirmed → Invalid
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.