#3631 Failing to save a user marks subdomain as offline

Created 7 months ago by jhrozek
Modified a month ago

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.

6 months ago

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

6 months ago

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

a month ago

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

Login to comment on this ticket.

cancel