Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1087831

Summary: Environment groups specified in kickstart are not ticked in the GUI
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kolman <mkolman>
Component: anacondaAssignee: Martin Kolman <mkolman>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: atodorov, jstodola, mbanas, mkolman, mkovarik
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-21.48.22.7-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 09:46:45 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:
Bug Depends On:    
Bug Blocks: 1205794    
Attachments:
Description Flags
software selection spoke none

Description Martin Kolman 2014-04-15 12:17:21 UTC 
Description of problem:
Environment groups specified in kickstart are not ticked in the software selection spoke group list.


How reproducible:
always


Steps to Reproduce:
1. specify some groups in the kickstart
2. start the installation
3. go the to the software selection spoke

Actual results:
No groups are ticked in the group list.


Expected results:
The groups specified in kickstart are ticked in the group list.

Additional info:
Even though the the groups don't appear to be ticked/selected in the GUI, they are still correctly installed once installation is started. But this can still be rather confusing for the user.
Comment 2 Ludek Smid 2014-06-26 10:54:38 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Comment 3 Ludek Smid 2014-06-26 11:15:55 UTC 
The comment above is incorrect. The correct version is bellow.
I'm sorry for any inconvenience.
---------------------------------------------------------------

This request was NOT resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you need
to escalate this bug.
Comment 5 Alexander Todorov 2014-11-25 11:45:06 UTC 
With anaconda-19.31.109-1 and kickstart containing:

%packages
@kde-desktop
@java-platform
%end


My ks.cfg is deliberately missing some info so that it stops at the hub spoke. If I go to the software selection spoke, click on the Server with GUI environment and scroll down the group list to where KDE and Java Platform groups are they appear unselected.
Comment 6 Martin Kolman 2014-11-25 12:52:53 UTC 
(In reply to Alexander Todorov from comment #5)
> With anaconda-19.31.109-1 and kickstart containing:
> 
> %packages
> @kde-desktop
> @java-platform
> %end
> 
> 
> My ks.cfg is deliberately missing some info so that it stops at the hub
> spoke. If I go to the software selection spoke, click on the Server with GUI
> environment and scroll down the group list to where KDE and Java Platform
> groups are they appear unselected.

Actually those are groups (marked just with leading "@") - environments are marked with "@^".

For more info:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-packages
Comment 7 Alexander Todorov 2014-11-26 07:44:37 UTC 
Created attachment 961517 [details]
software selection spoke

Re-tested with:

%packages
@^Infrastructure Server
%end


Infrastructure Server environment was highlighted but the radio button on the left of it was not selected. See the attached screenshot.
Comment 8 Martin Kolman 2015-01-06 15:17:50 UTC 
A patch has just been sent for review that makes sure that the radio button is ticked for the environment selected in kickstart.
Comment 12 Martin Kolman 2015-06-23 12:34:59 UTC 
Works fine with Anaconda 21.48.22.7-1. If the following Kickstart is used:

%packages
@^infrastructure-server-environment
%end

the Infrastructure Server is correctly selected in the listview on the left.
Comment 15 errata-xmlrpc 2015-11-19 09:46:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2284.html