QA:Testcase Anaconda User Interface VNC Vncconnect
This test verifies the vnc option vncconnect work as expected. See Anaconda_Boot_Options for more information.
- Requires two systems able to communicate over the network, one to test the installation and a second to initiate the VNC client session
- Install a VNC client application. The package
can be used.
sudo dnf install tigervnc
How to test
- Boot the installer with the command-line option to connect the client named <host>, and optionally use port <port> (added as a kernel option in boot selection screen):
- On another system that is accessible over the network, start a VNC client with reverse connections enabled. If using
), use the following example. The command
vinagremay also be used.
vncviewer -listen [port]
- Using the VNC client session, complete the installation as desired
- Anaconda starts and attempts to initiate a VNC connection on the specified
Running anaconda 15.31, the Fedora system installer - please wait. 09:16:44 Starting VNC... 09:16:45 The VNC server is now running. 09:16:45 You chose to connect to a listening vncviewer. This does not require a password to be set. If you set a password, it will be used in case the connection to the vncviewer is unsuccessful 09:16:45 Attempting to connect to vnc client on host 192.168.1.17... 09:16:45 Will try to connect again in 15 seconds... 09:17:00 Will try to connect again in 15 seconds...
- After starting the VNC client with reverse connections enabled, a successful VNC connection is established between the installing system, and your VNC client. Output similar to the following will be visible on the installing systems console.
09:17:15 Connected! Press <enter> for a shell 09:17:15 Starting graphical installation.
- VNC works normally during installation (mouse, keyboard)
- Anaconda completes successfully
- The installed system boots into runlevel 3 (no graphical session)