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

sssd-ad-2.8.2-13.ph5.x86_64.rpm fails to load AD module #1581

Open
novaksam opened this issue Jan 3, 2025 · 0 comments
Open

sssd-ad-2.8.2-13.ph5.x86_64.rpm fails to load AD module #1581

novaksam opened this issue Jan 3, 2025 · 0 comments
Labels

Comments

@novaksam
Copy link

novaksam commented Jan 3, 2025

Describe the bug

There appears to be a bug in the latest sssd-ad update. When i attempt to start/restart sssd with AD set as the identity provider the logging for the AD module produces the following (at the end of the log):

  • (2025-01-03 13:28:16): [be[uwsp.edu]] [dp_load_module] (0x0400): About to load module [ad].
  • (2025-01-03 13:28:16): [be[uwsp.edu]] [dp_module_open_lib] (0x1000): Loading module [ad] with path [/usr/lib/sssd/libsss_ad.so]
  • (2025-01-03 13:28:16): [be[uwsp.edu]] [dp_module_open_lib] (0x0010): Unable to load module [ad] with path [/usr/lib/sssd/libsss_ad.so]: /usr/lib/sssd/libsss_ad.so: undefined symbol: sdap_iphost_handler_send

Downgrading to sssd-ad-2.8.2-12.ph5.x86_64.rpm resolved the issue

Specifically I did tdnf --enablerepo=photon downgrade sssd-ad

Reproduction steps

systemctl restart sssd

Expected behavior

SSSD starts correctly.

Additional context

No response

@novaksam novaksam added the bug label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant