Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1309111

Summary: Package environment ID required in kickstart
Product: [Retired] Fedora Documentation Reporter: David Galloway <dgallowa>
Component: install-guideAssignee: Jaromir Hradilek <jhradile>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: pbokoc, zach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 09:21:52 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 David Galloway 2016-02-16 21:56:40 UTC
Description of problem:
Documentation states a package environment's name can be specified in a kickstart when the ID is required instead.

https://docs.fedoraproject.org/en-US/Fedora/22/html/Installation_Guide/sect-kickstart-packages.html

@^Infrastructure Server <- does not work

@^infrastructure-server-environment <- works

Version-Release number of selected component (if applicable):
Fedora 22

How reproducible:
Every time

Steps to Reproduce:
1. Create kickstart specifying @^Infrastructure Server in %packages
2. Start install

Actual results:
You have specified that the group 'Infrastructure Server' should be installed.
This group does not exist.  Would you like to ignore this group and continue with installation?
Please respond 'yes' or 'no': 

Expected results:
Group/Environment get installed

Additional info:

Comment 2 Petr Bokoc 2024-05-21 09:21:52 UTC
The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.