Skip to content

Commit

Permalink
ad: do not print backtrace if SOM is missing in GPO
Browse files Browse the repository at this point in the history
This is expected on empty GPOs and we just skip the element.
Therefore we should not print backtrace.
  • Loading branch information
pbrezina committed Nov 14, 2023
1 parent 47743e2 commit fe6ab54
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/providers/ad/ad_gpo.c
Original file line number Diff line number Diff line change
Expand Up @@ -3435,7 +3435,7 @@ ad_gpo_get_som_attrs_done(struct tevent_req *subreq)
goto done;
}
if ((num_results < 1) || (results == NULL)) {
DEBUG(SSSDBG_OP_FAILURE, "no attrs found for SOM; try next SOM.\n");
DEBUG(SSSDBG_MINOR_FAILURE, "no attrs found for SOM; try next SOM.\n");
state->som_index++;
ret = ad_gpo_get_som_attrs_step(req);
goto done;
Expand All @@ -3456,7 +3456,7 @@ ad_gpo_get_som_attrs_done(struct tevent_req *subreq)
}

if ((ret == ENOENT) || (el->num_values == 0)) {
DEBUG(SSSDBG_OP_FAILURE, "no attrs found for SOM; try next SOM\n");
DEBUG(SSSDBG_MINOR_FAILURE, "no attrs found for SOM; try next SOM\n");
state->som_index++;
ret = ad_gpo_get_som_attrs_step(req);
goto done;
Expand Down

0 comments on commit fe6ab54

Please sign in to comment.