sss_groupadd no longer detects duplicate GID numbers

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1335

• Created at 2012-05-11 18:02:59 by jhrozek
• Closed as Fixed
• Assigned to jhrozek
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=821044

---

https://bugzilla.redhat.com/show_bug.cgi?id=821044 (Red Hat Enterprise Linux 6)

Description of problem:
In 6.2, sss_groupadd used to warn if there was a duplicate name or GID.
sss_groupadd no longer warns about duplicate GID numbers in 6.3

Version-Release number of selected component (if applicable):
1.8.0-25

How reproducible:
always

Steps to Reproduce:
1. sss_groupadd -g 1234 groupone
2. sss_groupadd -g 1234 grouptwo
3.

Actual results:
groupone disappears from the cache, grouptwo is saved with requested GID of
1234. No warning issues

Expected results:
grouptwo should not be added and sss_groupadd should print a warning

Additional info:
This is a regression caused by a fix for
https://bugzilla.redhat.com/show_bug.cgi?id=746181

When QE tests this bug, it would be prudent to retest #746181, too.

Comments

---

Comment from sgallagh at 2012-05-11 18:22:18

Fields changed

blockedby: =>
blocking: =>
component: SSSD => SysDB
coverity: =>
feature_milestone: =>
milestone: NEEDS_TRIAGE => SSSD 1.8.4 (LTM)
owner: somebody => jhrozek
priority: major => blocker
tests: => 0
testsupdated: => 0
upgrade: => 0
version: => 1.8.0

---

Comment from sgallagh at 2012-05-11 18:22:49

Fixed by:
- 79a93ba (master)
- 4f2d70c (sssd-1-8)

resolution: => fixed
status: new => closed

---

Comment from jhrozek at 2017-02-24 14:56:42

Metadata Update from @jhrozek:

• Issue assigned to jhrozek
• Issue set to the milestone: SSSD 1.8.4 (LTM)