#2543 GPO code fails if no LDAP URI can be resolved
Closed: Fixed None Opened 4 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

2 years ago

Login to comment on this ticket.

Metadata