RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1221986 - openstack-nova-novncproxy fails to start
Summary: openstack-nova-novncproxy fails to start
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: rdo-manager
Version: trunk
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: Ben Nemec
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-15 12:12 UTC by Marius Cornea
Modified: 2016-05-19 15:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:43:06 UTC
Embargoed:


Attachments (Terms of Use)
novncproxy.error (1.42 KB, text/plain)
2015-05-15 12:12 UTC, Marius Cornea
no flags Details

Description Marius Cornea 2015-05-15 12:12:12 UTC
Created attachment 1025818 [details]
novncproxy.error

Description of problem:
openstack-nova-novncproxy fails to start because it's trying to listen on all interfaces on port 6080 which conflicts with haproxy.

Version-Release number of selected component (if applicable):
CentOS 7.1
instack-0.0.6-post6.el7.centos.noarch
openstack-tripleo-heat-templates-0.8.6-dev5.el7.centos.noarch
openstack-tripleo-puppet-elements-0.0.1-dev63.el7.centos.noarch
openstack-puppet-modules-2015.1.0-2.el7.noarch

How reproducible:
TripleO installation on virtual env according to https://repos.fedorapeople.org/repos/openstack-m/docs/master/

Steps to Reproduce:
1. Follow steps in the docs to get the overcloud deployed on CentOS 7.1
2. Log in the overcloud controller node
3. systemctl status openstack-nova-novncproxy.service 

Actual results:
Service fails to start. Log shows error: [Errno 98] Address already in us

Expected results:
The openstack-nova-novncproxy service starts.

Additional info:

The nova-novncproxy is trying to listen on all interfaces port 6080 and haproxy is already using 2 IP addresses to listen on port 6080. 

[root@ov-3sumit5kzsi-0-pvuhwrt7pa3y-controller-e6ywftkcqchy ~]# grep -v '^$\|^\s*\#' /etc/nova/nova.conf | grep novnc
novncproxy_host=0.0.0.0
novncproxy_port=6080
novncproxy_base_url=http://0.0.0.0:6080/vnc_auto.html

[root@ov-3sumit5kzsi-0-pvuhwrt7pa3y-controller-e6ywftkcqchy ~]# grep -A4 nova_novncproxy /etc/haproxy/haproxy.cfg 
listen nova_novncproxy
  bind 192.0.2.10:6080 
  bind 192.0.2.11:6080 
  option httpchk GET /
  server 192.0.2.13 192.0.2.13:6080 check fall 5 inter 2000 rise 2

Replacing novncproxy_host=0.0.0.0 with novncproxy_host=192.0.2.13 in /etc/nova/nova.conf makes it start up successfully. 

Log is attached.

Comment 1 Ben Nemec 2015-05-15 17:57:23 UTC
I believe https://review.openstack.org/#/c/183630 should fix this.

Comment 4 Chandan Kumar 2016-05-19 15:43:06 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.