Bug 1212578

Summary: method=vnc does not work with RHEL7
Product: [Retired] Beaker Reporter: Jeff Bastian <jbastian>
Component: generalAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact: Anwesha Chatterjee <achatter>
Severity: medium Docs Contact:
Priority: low    
Version: developCC: achatter, dcallagh, ebaak, rjoost
Target Milestone: 25.0Keywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-19 04:19:09 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 Jeff Bastian 2015-04-16 17:16:52 UTC
Description of problem:
I tried to do a manual installation with VNC of RHEL7 using
    ks_meta="manual mode=vnc"
but RHEL7 anaconda refused to start VNC
    Not asking for VNC because of an automated install

The minimalist kickstart generated is only two lines:
    nfs --server server.example.com --dir /RHEL-7/7.1/Server/x86_64/os/
    ignoredisk --interactive

I tried again using my own kickstart section (instead of using ks_meta) with "vnc" added:
    <kickstart>
        <![CDATA[
        nfs --server server.example.com --dir /RHEL-7/7.1/Server/x86_64/os/
        vnc
        ignoredisk --interactive
        ]]>
    </kickstart>

This time it worked.
    Please manually connect your vnc client to client.example.com:1
    (192.168.1.1:1) to begin the install.

Please add "vnc" to the minimalist kickstart file when doing ks_meta="manual mode=vnc" with RHEL7.

Comment 2 Dan Callaghan 2017-10-23 07:13:22 UTC
https://gerrit.beaker-project.org/5887

Comment 4 Anwesha Chatterjee 2017-11-27 04:04:52 UTC
Verified by running https://beaker-devel.app.eng.bos.redhat.com/jobs/13166
and connecting to Anaconda interface through VNC successfully and completing the installation.

Comment 5 Dan Callaghan 2018-02-06 00:36:06 UTC
This bug was fixed on the release-24 branch, to appear in Beaker 24.6, but we are not planning any more maintenance releases for the 24.x series. The next release will be Beaker 25.0. Updating the milestone accordingly.

Comment 6 Roman Joost 2018-03-19 04:19:09 UTC
Beaker 25.0 has been released.

Release notes are available upstream: https://beaker-project.org/docs/whats-new/release-25.html