sssd-devel July 2021

sssd-devel@lists.fedorahosted.org

2 participants
71 discussions

[sssd PR#5674][opened] [WIP] This is just a test
by ikerexxe 16 Jan '22

16 Jan '22

URL: https://github.com/SSSD/sssd/pull/5674 Author: ikerexxe Title: #5674: [WIP] This is just a test Action: opened PR body: """ This is just a test for Deepak's latest PR, which fails in CI. """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5674/head:pr5674 git checkout pr5674

2 4

[sssd PR#175][opened] Add module for starting services
by lslebodn 22 Nov '21

22 Nov '21

URL: https://github.com/SSSD/sssd/pull/175 Author: lslebodn Title: #175: Add module for starting services Action: opened PR body: """ This is a WIP version of reducing code duplication in our cwrap integration tests. I am still not sure whether we should also reuse function `create_sssd_fixture`. And if yes; then probably in different nodule then `services` And comments are welcome. BTW I wrote patches few weeks ago; therefore new tests are not converted. I am just sending patches to get some feedback. Site effect of this patches is that tests are cca 20% faster (IIRC) """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/175/head:pr175 git checkout pr175

5 5

[sssd PR#5712][opened] Health and Support Analyzer - Add request log parsing utility
by justin-stephenson 14 Oct '21

14 Oct '21

URL: https://github.com/SSSD/sssd/pull/5712 Author: justin-stephenson Title: #5712: Health and Support Analyzer - Add request log parsing utility Action: opened PR body: """ * Print client command request list, NSS (default), or PAM ~~~ $ sssctl analyze request --list $ sssctl analyze request --list --pam ~~~ * Track individual NSS request ~~~ $ sssctl analyze request --cid=20 ~~~ * Track individual NSS request including cache request logs ~~~ $ sssctl analyze request --cid=20 --cachereq ~~~ * Track individual PAM request ~~~ $ sssctl analyze request --cid=20 --pam ~~~ * Supports --logger=journald, pending tevent chain ID support for logger=journald ~~~ $ sssctl analyze --source=journald request --list ~~~ * Analyze logs extracted, or sent from another user (CEE use case). Logs must be from compatible SSSD version with REQ_TRACE log messages and tevent chain ID support ~~~ $ sssctl analyze --logdir=/path/to/sosreport/var/log/sssd request --list ~~~ """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5712/head:pr5712 git checkout pr5712

5 86

[sssd PR#5434][opened] Adding multihost tests for ad_allow_remote_domain_local_groups, bz1883488 bz1756240
by sidecontrol 13 Oct '21

13 Oct '21

URL: https://github.com/SSSD/sssd/pull/5434 Author: sidecontrol Title: #5434: Adding multihost tests for ad_allow_remote_domain_local_groups, bz1883488 bz1756240 Action: opened PR body: """ This is the first multihost test that requires more than one AD server, it requires a root, child and tree domain and users created from the playbooks in CI. """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5434/head:pr5434 git checkout pr5434

4 15

[sssd PR#5722][opened] NSS client: avoid using NETDB_INTERNAL if daemon is not available
by grawity 06 Oct '21

06 Oct '21

URL: https://github.com/SSSD/sssd/pull/5722 Author: grawity Title: #5722: NSS client: avoid using NETDB_INTERNAL if daemon is not available Action: opened PR body: """ It seems that returning NETDB_INTERNAL as h_errno will cause glibc's getaddrinfo() to immediately return EAI_SYSTEM *without* falling through to other configured NSS modules. This means that if /etc/nsswitch.conf has 'sss' listed before 'dns' (for example), hostname resolution will be completely broken whenever SSSD is not running. (Even hostname lookups done by SSSD itself will fail, as the _SSS_LOOPS environment variable merely forces errno=0 but the getaddrinfo() call as a whole still returns EAI_SYSTEM.) This commit makes the NSS client return h_errno=NO_RECOVERY, as that's what systemd's nss-resolve and nss-mymachines seem to be doing. """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5722/head:pr5722 git checkout pr5722

5 12

[sssd PR#5473][opened] Tests: alltests: Check default debug level of sssd and corresponding logs
by madhuriupadhye 05 Oct '21

05 Oct '21

URL: https://github.com/SSSD/sssd/pull/5473 Author: madhuriupadhye Title: #5473: Tests: alltests: Check default debug level of sssd and corresponding logs Action: opened PR body: """ Check default debug level of sssd and corresponding logs It consists of four test cases: 1. Check the default debug level by authenticating the user 2. Check default level as 0 and 1 3. Check default level as 2 4. Check SBUS code triggers failure message during modules startup Verifies: Issues: #5422 #5425 Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1893159 https://bugzilla.redhat.com/show_bug.cgi?id=1915319 Signed-off-by: Madhuri Upadhye <mupadhye(a)redhat.com> """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5473/head:pr5473 git checkout pr5473

4 17

[sssd PR#5684][opened] src/conf_macros.m4: set default value /run for pidpath
by kkang-wr 05 Oct '21

05 Oct '21

URL: https://github.com/SSSD/sssd/pull/5684 Author: kkang-wr Title: #5684: src/conf_macros.m4: set default value /run for pidpath Action: opened PR body: """ /var/run is deprecated, so replace /var/run with /run as the default value of variable pidpath. Signed-off-by: Kai Kang <kai.kang(a)windriver.com> """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5684/head:pr5684 git checkout pr5684

4 8

[sssd PR#5636][opened] Improve assertion when verifying paths for Python modules
by sergiodj 05 Oct '21

05 Oct '21

URL: https://github.com/SSSD/sssd/pull/5636 Author: sergiodj Title: #5636: Improve assertion when verifying paths for Python modules Action: opened PR body: """ In Ubuntu we're facing a problem where the 3 Python tests under src/tests/*-test.py are failing due to cosmetical differences between what the '.__file__' method returns and what 'MODPATH' ends up being. I have not been able to pinpoint exactly what is causing this issue; it only happens when SSSD is built inside a chroot environment (with sbuild, for example). The logs look like this: ```python F ====================================================================== FAIL: testImport (__main__.PyHbacImport) Import the module and assert it comes from tree ---------------------------------------------------------------------- Traceback (most recent call last): File "/<<PKGBUILDDIR>>/src/tests/pyhbac-test.py", line 91, in testImport self.assertEqual(pyhbac.__file__, MODPATH + "/pyhbac.so") AssertionError: '/<<PKGBUILDDIR>>/build/./tp_pyhbac_xw2omut2/pyhbac.so' != './tp_pyhbac_xw2omut2/pyhbac.so' - /<<PKGBUILDDIR>>/build/./tp_pyhbac_xw2omut2/pyhbac.so + ./tp_pyhbac_xw2omut2/pyhbac.so ``` Given that the intention of the test is to verify that the two paths are equal, I suggest that we do this slight improvement and call 'os.path.realpath' before comparing both paths. This way we guarantee that they're both properly canonicalized. I have verified that the tests still pass with this change. """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5636/head:pr5636 git checkout pr5636

4 17

[sssd PR#5651][opened] TEST: Use absolute path for the MODPATH assertions in python tests
by mtorromeo 05 Oct '21

05 Oct '21

URL: https://github.com/SSSD/sssd/pull/5651 Author: mtorromeo Title: #5651: TEST: Use absolute path for the MODPATH assertions in python tests Action: opened PR body: """ Since 2.5.0 I had these 3 tests fail with the following assertion error: ``` ====================================================================== FAIL: testImport (__main__.PyHbacImport) Import the module and assert it comes from tree ---------------------------------------------------------------------- Traceback (most recent call last): File "/build/sssd/src/sssd-2.5.0/src/tests/pyhbac-test.py", line 91, in testImport self.assertEqual(pyhbac.__file__, MODPATH + "/pyhbac.so") AssertionError: '/build/sssd/src/sssd-2.5.0/./tp_pyhbac_za3ox6lp/pyhbac.so' != './tp_pyhbac_za3ox6lp/pyhbac.so' - /build/sssd/src/sssd-2.5.0/./tp_pyhbac_za3ox6lp/pyhbac.so + ./tp_pyhbac_za3ox6lp/pyhbac.so ``` I don't know what changed but the issue here is related to a long-standing bug [1] in `tempfile.mkdtemp` where the returned path is not absolute if the dir parameter is relative, despite the documentation saying that the returned path is always absolute. [1] https://bugs.python.org/issue7325 """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5651/head:pr5651 git checkout pr5651

3 17

[sssd PR#5724][opened] [WIP] SDAP: Continue when parsing entry fails
by elkoniu 04 Oct '21

04 Oct '21

URL: https://github.com/SSSD/sssd/pull/5724 Author: elkoniu Title: #5724: [WIP] SDAP: Continue when parsing entry fails Action: opened PR body: """ Configuration: IPA data provider with AD trust enabled In some scenarios when processing entry fail it may lead to marking the whole backend as offline. This PR implements skipping broken entries instead of triggering fail. Resolves: https://github.com/SSSD/sssd/issues/4893 """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/5724/head:pr5724 git checkout pr5724

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

sssd-devel July 2021