April 2022 - Sssd-maintainers - Fedora mailing-lists

[Bug 1965818] New: sssd - failing on "dotted"languages (Example turkish language)
by bugzilla＠redhat.com 22 Jun '22

22 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1965818 Bug ID: 1965818 Summary: sssd - failing on "dotted"languages (Example turkish language) Product: Fedora Version: 34 Hardware: x86_64 OS: Linux Status: NEW Component: sssd Severity: high Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: thunderbirdtr(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, jhrozek(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: Hello, SSSD Service isn't starting If we use dotted language in our system. For example, adding "LANG=tr_TR" into "/etc/sysconfig/sssd" makes sssd fails on start. If anyone install Fedora with "turkish" or other dotted language in their pc/laptop, that makes sssd fails on start. After I made little bit research, I notice this issue has been addressed multiple times around RHEL[0] and samba[1] and github[2] as well. So for that reason at least can we add "english" locale setting into rpm spec with "language" check as a workaround has been suggest in github link.That is at least gives us "working" package in dotted languge, and If anyone wants change setting, they can change it. At least for normal users, we can have working sssd service and not complain about fails all the times. I know this isn't the cleanest solution (proper solution is patching libldb package which causing this issue, but at least we can have a "quick&dirty" solution avoid on new installs. Thank you. [0] : https://bugzilla.redhat.com/show_bug.cgi?id=1743531 [1] : https://lists.samba.org/archive/samba-technical/2019-December/134659.html [2] : https://github.com/SSSD/sssd/issues/5285 Version-Release number of selected component (if applicable): sssd-2.5.0-2.fc34.x86_64 libldb-2.3.0-2.fc34.x86_64 How reproducible: Steps to Reproduce: 1. Install Fedora or change language into dotted or change "LANG" env into dotted langauge 2. reset sssd counter 3. start sssd Actual results: sssd fails Expected results: sssd should start clean in default config. Additional info: SSSD Systemctl errors systemd[1]: Starting System Security Services Daemon... sssd[760632]: Starting up systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION systemd[1]: sssd.service: Failed with result 'exit-code'. systemd[1]: Failed to start System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: sssd.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: Starting System Security Services Daemon... sssd[760633]: Starting up systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION systemd[1]: sssd.service: Failed with result 'exit-code'. systemd[1]: Failed to start System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: sssd.service: Scheduled restart job, restart counter is at 2. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: Stopped System Security Services Daemon. systemd[1]: Starting System Security Services Daemon... sssd[760636]: Starting up systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION systemd[1]: sssd.service: Failed with result 'exit-code'. systemd[1]: Failed to start System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: sssd.service: Scheduled restart job, restart counter is at 3. systemd[1]: Stopped System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: Starting System Security Services Daemon... sssd[760637]: Starting up systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION systemd[1]: sssd.service: Failed with result 'exit-code'. systemd[1]: Failed to start System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: sssd.service: Scheduled restart job, restart counter is at 4. systemd[1]: Stopped System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' systemd[1]: Starting System Security Services Daemon... sssd[760639]: Starting up systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION systemd[1]: sssd.service: Failed with result 'exit-code'. systemd[1]: Failed to start System Security Services Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' ----------- /var/log/sssd/sssd.log (last error with LANG setting is tr_TR (LANG=tr_TR) ) ----------- ********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE: * (2021-05-30 15:46:52): [sssd] [check_file] (0x0400): lstat for [/run/sssd.pid] failed: [2][No such file or directory]. * (2021-05-30 15:46:52): [sssd] [check_file] (0x0400): lstat for [/var/run/nscd/socket] failed: [2][No such file or directory]. * (2021-05-30 15:46:52): [sssd] [ldb] (0x0400): server_sort:Unable to register control with rootdse! * (2021-05-30 15:46:52): [sssd] [sss_ini_open] (0x0400): No /etc/sssd/sssd.conf. * (2021-05-30 15:46:52): [sssd] [sss_ini_read_sssd_conf] (0x0100): File /etc/sssd/sssd.conf does not exist. * (2021-05-30 15:46:52): [sssd] [confdb_ldif_from_ini_file] (0x0100): Value of config_file_version option not found. Assumed to be version 2. * (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x0400): Processing config section [sssd] * (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x0400): Processing attribute [services] * (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x4000): services: nss * (2021-05-30 15:46:52): [sssd] [sss_confdb_create_ldif] (0x4000): Section dn dn: cn=sssd,cn=config cn: sssd services: nss * (2021-05-30 15:46:52): [sssd] [confdb_init_db] (0x0100): LDIF file to import: dn: cn=config version: 2 dn: cn=sssd,cn=config cn: sssd services: nss * (2021-05-30 15:46:52): [sssd] [add_implicit_services] (0x0040): No domains configured! * (2021-05-30 15:46:52): [sssd] [get_monitor_config] (0x0040): Failed to add implicit configured services. Some functionality might be missing * (2021-05-30 15:46:53): [sssd] [confdb_expand_app_domains] (0x2000): implicit_files is not an app domain * (2021-05-30 15:46:53): [sssd] [confdb_get_domain_internal] (0x0400): No enumeration for [implicit_files]! * (2021-05-30 15:46:53): [sssd] [confdb_get_domain_internal] (0x0400): Please note that when enumeration is disabled `getent passwd` does not return all users by design. See sssd.conf man page for more detailed information * (2021-05-30 15:46:53): [sssd] [confdb_get_domain_internal] (0x1000): pwd_expiration_warning is -1 * (2021-05-30 15:46:53): [sssd] [server_setup] (0x0080): Failed setting process group: Operation not permitted[1]. We might leak processes in case of failure * (2021-05-30 15:46:53): [sssd] [become_user] (0x0200): Trying to become user [0][0]. * (2021-05-30 15:46:53): [sssd] [become_user] (0x0200): Already user [0]. * (2021-05-30 15:46:53): [sssd] [ldb] (0x0400): server_sort:Unable to register control with rootdse! * (2021-05-30 15:46:53): [sssd] [server_setup] (0x0400): CONFDB: /var/lib/sss/db/config.ldb * (2021-05-30 15:46:53): [sssd] [confdb_get_enabled_domain_list] (0x0040): Failed to get [domains] from [sssd], error [2] (Böyle bir dosya ya da dizin yok) ********************** BACKTRACE DUMP ENDS HERE ********************************* (2021-05-30 15:46:53): [sssd] [main] (0x0010): No domains configured. ********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE: * (2021-05-30 15:46:53): [sssd] [confdb_get_domains] (0x0080): No domains configured, fatal error! * (2021-05-30 15:46:53): [sssd] [main] (0x0010): No domains configured. ********************** BACKTRACE DUMP ENDS HERE ********************************* -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 8

[Bug 2077856] New: package sssd-idp-2.7.0-1.fc35.x86_64 requires sssd-common = 2.7.0-1.fc35, but none of the providers can be installed
by bugzilla＠redhat.com 02 May '22

02 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=2077856 Bug ID: 2077856 Summary: package sssd-idp-2.7.0-1.fc35.x86_64 requires sssd-common = 2.7.0-1.fc35, but none of the providers can be installed Product: Fedora Version: 36 Status: NEW Component: sssd Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: kparal(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, jhrozek(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: When trying to upgrade from F35 to F36: Error: Problem: package sssd-idp-2.7.0-1.fc35.x86_64 requires sssd-common = 2.7.0-1.fc35, but none of the providers can be installed - sssd-common-2.7.0-1.fc35.x86_64 does not belong to a distupgrade repository - problem with installed package sssd-idp-2.7.0-1.fc35.x86_64 I believe that is resolved by pushing this update stable: https://bodhi.fedoraproject.org/updates/FEDORA-2022-cdc3365ffc Requesting for a Freeze Exception. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2077856

1 13

[GitHub] @pbrezina has invited you to join the @authselect organization
by GitHub 29 Apr '22

29 Apr '22

Hi sssd-bot, @pbrezina has invited you to join the @authselect organization on GitHub. Head over to https://github.com/authselect to check out @authselect’s profile. To join @authselect, follow this link: https://github.com/orgs/authselect/invitation?via_email=1 This invitation will expire in 7 days. Some helpful tips: - If you get a 404 page, make sure you’re signed in as sssd-bot. - You can also accept the invitation by visiting the organization page directly at https://github.com/authselect If you were not expecting this invitation, you can ignore this email. If @pbrezina is sending you too many emails, you can block them by visiting https://github.com/settings/blocked_users?block_user=pbrezina or report them for abuse at https://github.com/contact/report-abuse?report=pbrezina. Thanks, The GitHub Team To opt out of future invitations from @authselect, follow this link: https://github.com/orgs/authselect/opt-out

1 0

[Bug 2078243] New: sssd.conf files not came with sssd-common package anymore and service fails.
by bugzilla＠redhat.com 25 Apr '22

25 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=2078243 Bug ID: 2078243 Summary: sssd.conf files not came with sssd-common package anymore and service fails. Product: Fedora Version: 36 Status: NEW Component: sssd Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: thunderbirdtr(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, jhrozek(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora I freshly installed Fedora KDE 36 on VM and "sssd" service gives "condition failed" error. I have some problem on my current F36 machine as well. Package versions: sssd-common-2.6.3-1.fc36.x86_64 sssd-2.6.3-1.fc36.x86_64 Service Result systemctl status sssd ○ sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met I removed directory and re-installed and none of them worked. rpm -ql sssd-common | grep etc /etc/logrotate.d /etc/logrotate.d/sssd /etc/pam.d/sssd-shadowutils /etc/rwtab.d /etc/rwtab.d/sssd /etc/sssd /etc/sssd/conf.d /etc/sssd/pki /etc/sssd/sssd.conf Normally, I expect it should be up and running. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2078243

1 4

[Bug 2066681] New: test_inotify fails in Fedora Rawhide build
by bugzilla＠redhat.com 12 Apr '22

12 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=2066681 Bug ID: 2066681 Summary: test_inotify fails in Fedora Rawhide build Product: Fedora Version: rawhide Status: NEW Component: sssd Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: abokovoy(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, jhrozek(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora ================================== sssd 2.6.3: ./test-suite.log ================================== # TOTAL: 97 # PASS: 94 # SKIP: 2 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_inotify ================== [==========] Running 5 test(s). [ RUN ] test_inotify_mv [ OK ] test_inotify_mv [ RUN ] test_inotify_mod [ OK ] test_inotify_mod [ RUN ] test_inotify_del_add [ OK ] test_inotify_del_add [ RUN ] test_inotify_file_moved_in [sssd] [test_timeout] (0x0010): The test timed out! [ ERROR ] --- [ LINE ] --- src/tests/cmocka/test_inotify.c:54: error: Failure! [ FAILED ] test_inotify_file_moved_in [ RUN ] test_inotify_delay [ ERROR ] --- [ LINE ] --- src/tests/cmocka/test_inotify.c:483: error: Failure! [ FAILED ] test_inotify_delay [==========] 5 test(s) run. [ PASSED ] 3 test(s). [ FAILED ] 2 test(s), listed below: [ FAILED ] test_inotify_file_moved_in [ FAILED ] test_inotify_delay 2 FAILED TEST(S) FAIL test_inotify (exit status: 2) SKIP: src/tests/whitespace_test =============================== Git repository is required for this test! SKIP src/tests/whitespace_test (exit status: 77) SKIP: src/tests/double_semicolon_test ===================================== Git repository is required for this test! SKIP src/tests/double_semicolon_test (exit status: 77) ============================================================================ Testsuite summary for sssd 2.6.3 ============================================================================ # TOTAL: 97 # PASS: 94 # SKIP: 2 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See ./test-suite.log Please report to sssd-devel(a)lists.fedorahosted.org ============================================================================ make[4]: Leaving directory '/builddir/build/BUILD/sssd-2.6.3' make[4]: *** [Makefile:40966: test-suite.log] Error 1 make[3]: *** [Makefile:41074: check-TESTS] Error 2 make[2]: *** [Makefile:41955: check-am] Error 2 make[1]: *** [Makefile:40851: check-recursive] Error 1 make: *** [Makefile:41957: check] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.tw72wM (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.tw72wM (%check) Finish: rpmbuild sssd-2.6.3-101.20220317.1005.git9f3f55a12.fc37.src.rpm Finish: build phase for sssd-2.6.3-101.20220317.1005.git9f3f55a12.fc37.src.rpm INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/fedora-rawhide-x86_64-1647504626.128044/root/var/log/dnf.rpm.log /var/lib/mock/fedora-rawhide-x86_64-1647504626.128044/root/var/log/dnf.librepo.log /var/lib/mock/fedora-rawhide-x86_64-1647504626.128044/root/var/log/dnf.log -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2066681

1 11

[Bug 2066688] New: rawhide ships older sssd version than fc36
by bugzilla＠redhat.com 12 Apr '22

12 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=2066688 Bug ID: 2066688 Summary: rawhide ships older sssd version than fc36 Product: Fedora Version: rawhide Status: NEW Component: sssd Assignee: sssd-maintainers(a)lists.fedoraproject.org Reporter: frenaud(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: abokovoy(a)redhat.com, atikhono(a)redhat.com, jhrozek(a)redhat.com, lslebodn(a)redhat.com, luk.claes(a)gmail.com, mzidek(a)redhat.com, pbrezina(a)redhat.com, sbose(a)redhat.com, ssorce(a)redhat.com, sssd-maintainers(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: Fedora rawhide is shipping sssd version 2.6.2-3.fc36 while fedora 36 already has sssd-2.6.3-1.fc36. This old version is missing some fixes related to IPA-AD trust and our freeipa rawhide tests are failing because of it (https://github.com/SSSD/sssd/issues/5947 fixed in 2.6.3). Version-Release number of selected component (if applicable): sssd-client-2.6.2-3.fc36.x86_64 How reproducible: Steps to Reproduce: 1. install sssd on rawhide 2. # rpm -qa sssd-client sssd-client-2.6.2-3.fc36.x86_64 This issue was already discussed internally with SSSD developers, and is related to a build issue (make check failure). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2066688

1 5

2024

2023

2022

2021

2020

Sssd-maintainers April 2022