Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ad: avoid printing backtrace on certain conditions #7035

Closed
wants to merge 2 commits into from

Conversation

pbrezina
Copy link
Member

This was found by test from #6928.

@@ -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");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it mean "No GPO was found for given scope of management (SOM)"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIUC yes

@@ -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");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This message is the same as above and I think this is wrong.
Looking below I guess it should be something like "AD_AT_GPLINK attr not found or has no value"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack.

@alexey-tikhonov
Copy link
Member

If those are totally ok and aren't a sign of misconfiguration on server side, I would change to SSSDBG_FUNC_DATA or higher, not SSSDBG_MINOR_FAILURE

This is expected on empty GPOs and we just skip the element.
Therefore we should not print backtrace.
@pbrezina
Copy link
Member Author

Updated.

@alexey-tikhonov
Copy link
Member

ACK

Copy link
Contributor

@thalman thalman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

@alexey-tikhonov
Copy link
Member

Pushed PR: #7035

  • master
    • 3e976dc - ad: do not print backtrace if SOM is missing in GPO
    • 76d3b5a - ad: do not print backtrace if SSSD domain name is not the same as DNS name
  • sssd-2-9
    • eabeb3a - ad: do not print backtrace if SOM is missing in GPO
    • 35bcb91 - ad: do not print backtrace if SSSD domain name is not the same as DNS name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants