#2137 SSSD fails to fetch netgroup information with setnetgrent failed error
Closed: Fixed Opened by jhrozek.

A RHEL customer was having problems with saving netgroup when the SSSD failed over from one LDAP server to a replica that was out of sync and provided a different netgroup data than the primary server.


Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1022981 (Red Hat Enterprise Linux 6)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1025276 1025276] => [https://bugzilla.redhat.com/show_bug.cgi?id=1025276 1025276], [https://bugzilla.redhat.com/show_bug.cgi?id=1022981 1022981]

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.11.3
review: True => 0
selected: =>
testsupdated: => 0

Lukas is already looking into this issue.

owner: somebody => lslebodn

Fields changed

patch: 0 => 1
status: new => assigned

  • master: 9c83da3f27cb4473bd6bbc0167b471ed88acd842
  • sssd-1-11: 1914ad0701e58706ab277c822b5f057e34c00011

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => N/A, just a bugfix to handle a strange misconfiguration gracefully.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1243118 (Red Hat Enterprise Linux 5)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1025276 1025276], [https://bugzilla.redhat.com/show_bug.cgi?id=1022981 1022981] => [https://bugzilla.redhat.com/show_bug.cgi?id=1025276 1025276], [https://bugzilla.redhat.com/show_bug.cgi?id=1022981 1022981], [https://bugzilla.redhat.com/show_bug.cgi?id=1243118 1243118]

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.11.3

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3179

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata