This is an automatic backport of PR#8697 sdap: Reduce log level when get_naming_context() fails to branch sssd-2-13, created by @scabrero.

Please make sure this backport is correct.

You can push changes to this pull request

git remote add sssd-bot [email protected]:sssd-bot/sssd.git
git fetch sssd-bot refs/heads/SSSD-sssd-backport-pr8697-to-sssd-2-13
git checkout SSSD-sssd-backport-pr8697-to-sssd-2-13
git push sssd-bot SSSD-sssd-backport-pr8697-to-sssd-2-13 --force

Original commits
edf4a0f - sdap: Reduce log level when get_naming_context() fails

Backported commits

• 3d94983 - sdap: Reduce log level when get_naming_context() fails

Original Pull Request Body

When a plain LDAP server hosts multiple naming contexts but there is no defaultNamingContext in the rootdse, the following message is logged periodically:

[be[LDAP]] [sdap_set_config_options_with_rootdse] (0x0020): get_naming_context failed.

The message is logged at SSSDBG_CRIT_FAILURE level, which seems too high for a non-fatal failure:

        if (sdom->naming_context == NULL) {
            DEBUG(SSSDBG_CRIT_FAILURE, "get_naming_context failed.\n");

            /* This has to be non-fatal, since some servers offer
             * multiple namingContexts entries. We will just
             * add NULL checks for the search bases in the lookups.
             */
            ret = EOK;
            goto done;
        }