Bug 768318

Summary: RFE: Impossible to change VNC port (5901) with Anaconda installer
Product: [Fedora] Fedora Reporter: Peter Åstrand <astrand>
Component: anacondaAssignee: David Cantrell <dcantrell>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, dcantrell, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-04 00:00:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda.log none

Description Peter Åstrand 2011-12-16 10:51:38 UTC
The Anaconda version included in RHEL is older than the Fedora one. The VNC command line options are different. From: http://fedoraproject.org/wiki/Anaconda/Kickstart#vnc :

vnc [--host=<hostname>] [--port=<port>] [--password=<password>] 

However, the RHEL Anaconda only supports "vnc" and "vncpassword", making it impossible to specify another port than the standard 5901.

Comment 2 Chris Lumens 2011-12-16 15:28:36 UTC
The code in RHEL6 sure looks like this is supported.  Did you try?  Do you have any log files or error messages?

Comment 3 Peter Åstrand 2011-12-17 08:44:43 UTC
I tried changing "vnc vncpassword=something" to "vnc --password=something". This caused Anaconda to warn me about running without a password. Also, as far as I can see, the RHEL documentation only mentions the old syntax/options:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/sn-remoteaccess-installation.html#sn-remoteaccess-installation-vnc :

linux vnc vncpassword=qwerty

Comment 4 Chris Lumens 2011-12-20 04:08:34 UTC
That page describes command line options, not kickstart options.  In order to see what's going on here, I need your kickstart file and /tmp/anaconda.log.  You can remove any sensitive information like passwords from your kickstart file first.

Comment 5 Peter Åstrand 2011-12-20 08:10:40 UTC
It's a command line option that I want. I am not using Kickstart at all (except that I specify ks=file:/dev/null on the command line to work around bug 673864). Sorry for confusing you by referencing the Kickstart page, but I thought that the options were in sync. 

The complete command line I'm using is:

vnc --password=something ks=file:/dev/null

This causes Anaconde to print the error:

WARNING!!! VNC server running with NO PASSWORD!

Comment 6 Peter Åstrand 2011-12-20 08:11:05 UTC
Created attachment 548784 [details]
anaconda.log

Comment 7 Chris Lumens 2011-12-20 14:03:17 UTC
You're using the wrong command line option syntax, which is why I thought you were using kickstart.  You should be using vncpassword=something, instead of --password=something.  That's what the page you referenced in comment #3 is telling you to do.

Comment 8 Peter Åstrand 2011-12-20 15:16:59 UTC
Then we are back at the original problem: The lack of an option for specifying the port. A command line such as:

vnc vncport=4711

...does NOT work. And as I said, the documentation does not list any "vncport" option either. 

If there is a way of specifying the VNC port, then tell me how the command line should be.

Comment 9 David Cantrell 2011-12-20 15:50:10 UTC
The option you want is vncconnect=HOST:PORT

In a kickstart file, you can do:

    vnc --host=HOST --port=PORT --password=PASSWORD

The host and port specified refer to the vnc viewer that is already listening for the installer to connect to it.  If you want to pass this option on the boot command line, the syntax is:

    vnc vncconnect=HOST:PORT vncpassword=PASSWORD

The syntax is documented on this page:

    http://fedoraproject.org/wiki/Anaconda/Options

Using the host and port options for vnc mode requires that you have a VNC viewer running and listening on that port.

Comment 10 Peter Åstrand 2011-12-20 19:01:32 UTC
No. vncconnect is en entirely different thing, since it creates a reverse VNC connection. It's an entirely different thing. That does not work in my network scenario.

Comment 11 David Cantrell 2011-12-20 19:44:08 UTC
OK, well that's all anaconda has ever supported in terms of setting the VNC port.  Changing the product to Fedora as this is an upstream feature request.

Comment 12 Jesse Keating 2012-08-01 18:13:57 UTC
Patch posted to add this functionality to the boot time arguments.

Comment 13 Jesse Keating 2012-10-04 00:00:30 UTC
This can be done in branched composes now.