Bug 917316 - novnc not working
Summary: novnc not working
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: novnc
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nikola Dipanov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-03 03:05 UTC by Mohammed Arafa
Modified: 2016-04-22 05:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-13 11:19:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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!


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