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 1093071

Summary: anaconda does not recognize --gid as valid option in kickstart file
Product: Red Hat Enterprise Linux 7 Reporter: Paul Merchant <pmerchant.neulionwork>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0CC: pmerchant.neulionwork
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-02 13:41:44 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:
Attachments:
Description Flags
screenshot with error displayed
none
syslog
none
anaconda.log
none
program.log none

Description Paul Merchant 2014-04-30 14:24:20 UTC
Created attachment 891201 [details]
screenshot with error displayed

Description of problem:


Version-Release number of selected component (if applicable):
anaconda-19.31.77-1

How reproducible:


Steps to Reproduce:
1.Setup kickstart file with the following option included:
user --groups=wheel --homedir=/home/user1 --name=user1 --password=<hashhere> --iscrypted -uid=1010 --gid=1010 --gecos="user one"
2.Make kickstart file available via http
3.Boot VM from installation DVD
4.use following installation option: linux inst.ks=http://ipaddress/ks.cfg

Actual results:
no such option:  --gid

Expected results:
user created with the assigned gid

Additional info:
The kickstart installation works as expected if the --gid option is removed from the kickstart file user line.  The gid option did work on an interactive DVD install.  VM has 2 CPU and 1.5GB RAM assigned.

Comment 2 Brian Lane 2014-05-01 16:05:44 UTC
Please attach the logs from /tmp/*log as *individual* text/plain attachments to this bug. You can get to a shell by hitting ctrl-B 2

Comment 3 Paul Merchant 2014-05-01 21:57:54 UTC
Created attachment 891640 [details]
syslog

Comment 4 Paul Merchant 2014-05-01 21:58:47 UTC
Created attachment 891641 [details]
anaconda.log

Comment 5 Paul Merchant 2014-05-01 21:59:23 UTC
Created attachment 891642 [details]
program.log

Comment 6 Paul Merchant 2014-05-01 22:01:39 UTC
the ifcfg.log and the packaging.log were empty zero byte files.

Comment 7 Chris Lumens 2014-05-02 13:41:44 UTC

*** This bug has been marked as a duplicate of bug 1083928 ***