#3631 Failing to save a user marks subdomain as offline
Closed: cloned-to-github 2 years ago by pbrezina. Opened 4 years ago by jhrozek.

For example for a user who is missing a GID number:

(Wed Jan 24 13:11:55 2018) [sssd[be[DOMAIN]]] [sdap_save_user] (0x0020): Cannot retrieve GID for [user@domain] in domain [DOMAIN].
(Wed Jan 24 13:11:55 2018) [sssd[be[DOMAIN]]] [sdap_save_user] (0x0020): Failed to save user [user@domain]
(Wed Jan 24 13:11:55 2018) [sssd[be[DOMAIN]]] [ldb] (0x4000): cancel ldb transaction (nesting: 0)
(Wed Jan 24 13:11:55 2018) [sssd[be[DOMAIN]]] [sdap_id_op_done] (0x4000): releasing operation connection
(Wed Jan 24 13:11:55 2018) [sssd[be[DOMAIN]]] [ipa_srv_ad_acct_lookup_done] (0x0080): Sudomain lookup failed, will try to reset sudomain.

The reverse flow is:

- sdap_id_op_done()
- groups_by_user_done()
- sdap_get_initgr_recv()
- sdap_save_user()

I don't know if it makes sense to fix these issu es one-by-one or whether it would make more sense to get rid of using the sdap_id_op stuff completely.


Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.0

4 years ago

Metadata Update from @jhrozek:
- Issue priority set to: major

4 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

2 years ago

Metadata Update from @thalman:
- Issue tagged with: Future milestone

2 years ago

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/4652

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 Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata