Bug 1468101

Summary: [Regression] [Nova] Impossible to open vnc console for an instance
Product: Red Hat OpenStack Reporter: Nilesh <nchandek>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DUPLICATE QA Contact: Joe H. Rahme <jhakimra>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: berrange, dasmith, ealcaniz, eglynn, emilien, kchamart, sbauza, sferdjao, sgordon, srevivo, svanders, vromanso
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-07 13:43:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nilesh 2017-07-06 04:52:02 UTC
Description of problem:


I am not able to connect to a VNC console for any instance in Horizon. When going on the "console" tab for an instance, the window shows the vnc client but gets an error : "Failed to connect to server (code: 1006)"

After a short debug session, it appears that qemu-kvm binds on 127.0.0.1 for vnc consoles, blocking novncproxy service from connecting to the instance.
This conf is on compute node in /etc/nova/nova.conf (file attached) : vncserver_listen=127.0.0.1

I would like to know how to change this, with which parameter in Director template files, and what are the impact of changing this parameter.


In previous versions, default value for vncserver_listen was 0.0.0.0, allowing qemu-kvm to listen on all interfaces by default.
In OSP 10 (the version we have), default value is now 127.0.0.1, preventing connections from outside.

I also found that : https://bugs.launchpad.net/puppet-nova/+bug/1660099
I understand that a patch has been committed in Newton to change vncserver_listen IP address to internal_api network IP address. This is a real solution for us, but it seems that this solution is not in OSP 10.

We expect this solution to be in OSP 10 because it corresponds to our needs in terms of functionnality (recover access to consoles) and security (limiting to internal_api network).


Steps to Reproduce:
1.
2.
3.

Actual results:

We expect this solution to be in OSP 10 because it corresponds to our needs in terms of functionnality (recover access to consoles) and security (limiting to internal_api network).

Expected results:

We expect this solution to be in OSP 10 because it corresponds to our needs in terms of functionnality (recover access to consoles) and security (limiting to internal_api network).


Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2017-07-06 04:53:04 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 4 Sven Anderson 2017-07-07 13:43:06 UTC

*** This bug has been marked as a duplicate of bug 1431671 ***

Comment 5 awaugama 2017-09-07 19:01:42 UTC
Dup -- QE will decide about automating the original

Comment 6 Red Hat Bugzilla 2023-09-15 01:26:08 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days