Bug 465353

Summary:	anaconda says "connect to VNC" but does not tell where
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	anaconda-maint-list, dcantrell
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-11-01 23:18:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2008-10-02 21:04:37 UTC

Description of problem:

If one will try to start "VNC installation" while in "text mode"
then anaconda will say:

The VNC server is now running
Please manually connect your vnc client to begin the install.

but it leaves one guessing to connect where.  Especially
when network interfaces where configured by DHCP it may
be really non-obvious where a client may search for it.
True, it is possible to see the current configuration from
a shell running on another console but one has to be
aware of it and how to do this.  It would be really good
to have that information explicitly in a "connect" message.
A port in use also would be nice.

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

Comment 1 Chris Lumens 2008-10-03 17:43:05 UTC

It's supposed to be doing just that, but the display code for VNC fell out of sync with the many changes that have been happening with networking.  This will be fixed in the next build of anaconda.  Thanks for the report.

Comment 2 Michal Jaegermann 2008-11-01 17:41:59 UTC

I retried that with images dated 20081031.  Now the message says:

Please manually connect your vnc client to 0.0.0.0:1 to begin the install.

Does not seem to be much of improvement (or I miss something?). Is this a garbled IPv6 address of a loopback or this is what it looks it is?

BTW - 'netstat -t -a' seems to show that something does listen on 0.0.0.0:5901 although not on 5900. 'netstat -u -a' reports only bootpc.

Comment 3 David Cantrell 2008-11-01 23:18:43 UTC


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