Bug 917316

Summary:	novnc not working
Product:	[Fedora] Fedora EPEL	Reporter:	Mohammed Arafa <bugzilla>
Component:	novnc	Assignee:	Nikola Dipanov <ndipanov>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	aortega, eglynn, Jan.van.Eldik, jose.castro.leon, ndipanov, pbrady, p
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-13 11:19:52 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 Mohammed Arafa 2013-03-03 03:05:20 UTC

Description of problem:
i am hesitant to open this one. but i have verified my installation with other people in #openstack and have even gone as far as using a (modified of course) nova.conf file from a working ubuntu (devstack) installation.

all i know is vnc was working after i did an install. i had reason to redo my installation and it stopped working after that. i was under the impression i did something wrong however, i believe now it was an update. i dont know which update but approximately 1 to 2 months ago.

how is it broken? whenever i configure novnc to use an ip.. then i launch an instance i go to view the vnc console i find that it is failing to connect to 127.0.0.1 not the ip i configured in nova.conf

Version-Release number of selected component (if applicable):


How reproducible:
everytime

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mohammed Arafa 2013-09-13 10:42:29 UTC

fyi. i am now using rdo and it works for me out of the book. i am no longer inclined to set up a test machine with these settings. 

thank you very much

Comment 2 Pádraig Brady 2013-09-13 11:19:52 UTC

OK the novnc stuff has updated in the meantime, so we'll assume it's fixed for now. Thanks for the follow up!