From 1e2398870e8aa512ead3012d46cbe6252429467a Mon Sep 17 00:00:00 2001 From: Sumit Bose Date: Mon, 10 Sep 2018 15:35:45 +0200 Subject: [PATCH 16/83] intg: flush the SSSD caches to sync with files To make sure that SSSD has synced with the latest data added to the passwd file sss_cache is called in two places where the current sync scheme was not reliable. This was mainly observed when running the integration tests on Debian. Reviewed-by: Jakub Hrozek --- src/tests/intg/test_files_provider.py | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/tests/intg/test_files_provider.py b/src/tests/intg/test_files_provider.py index 9f30d2b..ead1cc4 100644 --- a/src/tests/intg/test_files_provider.py +++ b/src/tests/intg/test_files_provider.py @@ -644,6 +644,10 @@ def test_enum_users(setup_pw_with_canary, files_domain_only): user = user_generator(i) setup_pw_with_canary.useradd(**user) + # syncing with the help of the canary is not reliable after adding + # multiple users because the canary might still be in some caches so that + # the data is not refreshed properly. + subprocess.call(["sss_cache", "-E"]) sssd_getpwnam_sync(CANARY["name"]) user_list = call_sssd_enumeration() # +1 because the canary is added @@ -1043,6 +1047,10 @@ def test_getgrnam_add_remove_ghosts(setup_pw_with_canary, # Add this user and verify it's been added as a member pwd_ops.useradd(**USER2) + # The negative cache might still have user2 from the previous request, + # flushing the caches might help to prevent a failed lookup after adding + # the user. + subprocess.call(["sss_cache", "-E"]) res, groups = sssd_id_sync('user2') assert res == sssd_id.NssReturnCode.SUCCESS assert len(groups) == 2 -- 2.9.5