49dd8ee2834d9477418961dbaffa4a03cfa9fd1e |
|
29-Jan-2018 |
René Genz <liebundartig@freenet.de> |
Fix minor spelling mistakes in tests/*
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com> |
0558f270b3fbb0780e2a94602d455022b89f5381 |
|
01-Sep-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
TESTS: Test that ccaches can be stored after max_secrets is reached for regular non-ccache secrets
Test that even when we store the maximum number of secrets, we can still
store kerberos credentials, but only until we reach the max_secrets
limit as well.
Reviewed-by: Simo Sorce <simo@redhat.com>
Reviewed-by: Fabiano Fidêncio <fidencio@redhat.com> |
dc5da74112bde32b0bd33d9304f7e94eb8ed2885 |
|
18-Aug-2017 |
Lukas Slebodnik <lslebodn@redhat.com> |
intg: Increase startup timeouts for kcm and secrets
In cwrap environment, we start sssd_kcm and sssd_secrets ourself
and not by systemd socket activation. Our approach is to wait a second in
a loop till socket is available. However sometimes 1 second is not enough.
Patch increases wait timeout from 1 second to 10 and it seems to be enough even
when processes were executed with valgrind.
Traceback (most recent call last):
File "src/tests/intg/test_secrets.py", line 419, in setup_for_cli_timeout_test
return create_sssd_secrets_fixture(request)
File "src/tests/intg/test_secrets.py", line 82, in create_sssd_secrets_fixture
assert os.path.exists(sock_path)
AssertionError: assert False
+ where False = <function exists at 0x7f6c1cf520c8>('/tmp/sssd-intg.cdv0namx/var/run/secrets.socket')
+ where <function exists at 0x7f6c1cf520c8> = <module 'posixpath' from '/usr/lib64/python2.7/posixpath.pyc'>.exists
+ where <module 'posixpath' from '/usr/lib64/python2.7/posixpath.pyc'> = os.path
Resolves:
https://pagure.io/SSSD/sssd/issue/3481
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> |
5d9df623e1999864fd2873d8784a5182558f4a1f |
|
29-May-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
TESTS: Fix pep8 errors in test_kcm.py
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com>
Reviewed-by: Fabiano Fidêncio <fidencio@redhat.com> |
89726be5a05493b7af312f0be9ac5ecb6f1822e1 |
|
29-May-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
test_kcm: Remove commented code
The bug is now tracked with:
https://pagure.io/SSSD/sssd/issue/3413
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com> |
274489b092bba5fc81cb0f803843d56b267c5aaf |
|
24-May-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
TESTS: Add a test for parallel execution of klist
Integration test for:
https://pagure.io/SSSD/sssd/issue/3372
With https://pagure.io/SSSD/sssd/issue/3372 still broken, the unit test
wold fail because one of the concurrent klist commands would trigger a
race condition in the KCM queue code, crashing the KCM responder.
Reviewed-by: Pavel Březina <pbrezina@redhat.com> |
cac0db2f8004ae88b9263dc3888a11a2d3d3d114 |
|
27-Mar-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
KCM: Store ccaches in secrets
Adds a new KCM responder ccache back end that forwards all requests to
sssd-secrets.
Reviewed-by: Michal Židek <mzidek@redhat.com>
Reviewed-by: Simo Sorce <simo@redhat.com> |
0700118d8388c38b8cb28279510b206b76a3a411 |
|
27-Mar-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
TESTS: Add integration tests for the KCM responder
Reviewed-by: Michal Židek <mzidek@redhat.com>
Reviewed-by: Simo Sorce <simo@redhat.com>
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com> |