#3481 ERROR at setup of test_kcm_sec_init_list_destroy
Closed: Fixed Opened by fidencio.

Traceback (most recent call last):
File "/var/lib/jenkins/workspace/ci/label/fedora23/src/tests/intg/test_kcm.py", line 156, in setup_secrets
create_sssd_secrets_fixture(request)
File "/var/lib/jenkins/workspace/ci/label/fedora23/src/tests/intg/test_secrets.py", line 73, in create_sssd_secrets_fixture
assert os.path.exists(sock_path)
AssertionError: assert ('/tmp/sssd-intg.w7oj0b1i/var/run/secrets.socket')
+ where = .exists
+ where = os.path
==================== 221 passed, 1 error in 506.63 seconds =====================
Makefile:746: recipe for target 'intgcheck-installed' failed
make[2]: *** [intgcheck-installed] Error 1
make[2]: Leaving directory '/var/lib/jenkins/workspace/ci/label/fedora23/ci-build-debug/intg/bld/src/tests/intg'
Makefile:33715: recipe for target 'intgcheck-run' failed
make[1]: *** [intgcheck-run] Error 2
make[1]: Leaving directory '/var/lib/jenkins/workspace/ci/label/fedora23/ci-build-debug'
Makefile:33727: recipe for target 'intgcheck' failed
make: *** [intgcheck] Error 2

Happened on http://vm-058-233.${abc}/logs/job/73/41/fedora23/ci-build-debug/ci-make-intgcheck.log


https://github.com/SSSD/sssd/pull/350

Metadata Update from @lslebodn:
- Issue tagged with: PR

master:

  • dc5da74112bde32b0bd33d9304f7e94eb8ed2885

And secrets part also in 1.14 branch

sssd-1-14:

  • a5ce8c2502eff2bb3cb7bc532aab2f4e19662d5a

Metadata Update from @lslebodn:
- Issue set to the milestone: SSSD 1.15.4

Metadata Update from @lslebodn:
- Custom field version adjusted to 1.14.2

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4507

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata