#2543 GPO code fails if no LDAP URI can be resolved
Closed: Fixed None Opened 8 years ago by jhrozek.

If the AD client cannot even resolve the AD hostname (and thus no LDAP URI is resolved), then GPO code doesn't even reach the offline processing phase.

We should move checking the LDAP URI after the offline case to allow it to proceed even when DNS is acting up.

I have a patch.

owner: somebody => jhrozek
status: new => assigned

Fields changed

patch: 0 => 1

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.4

resolution: => fixed
status: assigned => closed

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

6 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/3585

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.

Login to comment on this ticket.