Bug 515671

Summary: 'groupadd -r' allocates gids upwards
Product: [Fedora] Fedora Reporter: Mark McLoughlin <markmc>
Component: shadow-utilsAssignee: Peter Vrabec <pvrabec>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 11CC: ovasik, pvrabec, tmraz, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 4.1.4.1-5.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-06 16:43:28 UTC Type: ---
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: 498968    

Description Mark McLoughlin 2009-08-05 10:28:23 UTC 
On F-11:

  $> rpm -q shadow-utils
  shadow-utils-4.1.2-13.fc11.i586
  $> groupadd -r foo
  $> getent group foo 
  foo:x:482:

with rawhide or F-11 updates-testing:

  $> rpm -q shadow-utils
  shadow-utils-4.1.4.1-5.fc12.x86_64
  $> groupadd -r foo
  $> getent group foo
  foo:x:106:

This is a serious problem because by allocating upwards, we're allocating in the 100-200 range which is now used by system accounts like qemu(107). See also bug #515667

The "allocate upwards" behaviour is long-standing, but it seems a recent shadow-utils re-base has broken it
Comment 1 Fedora Update System 2009-08-05 14:17:54 UTC 
shadow-utils-4.1.4.1-5.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/shadow-utils-4.1.4.1-5.fc11
Comment 2 Mark McLoughlin 2009-08-05 17:34:35 UTC 
Removing from F12VirtBlocker; using bug #515779 for F-12 tracking
Comment 3 Mark McLoughlin 2009-08-06 16:43:28 UTC 
Fixed in rawhide, f12-alpha tag request here:

  https://fedorahosted.org/rel-eng/ticket/2053
Comment 4 Fedora Update System 2009-08-12 20:52:36 UTC 
shadow-utils-4.1.4.1-5.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.