After srvcore merge, we can't setup SSL on Fedora 27 built from master.
Build tested: 389-ds-base-1.4.0.6-20180312git02a8defa8.fc27.x86_64
Reproduction steps: 1. Build 389-ds-base on clean Fedora 27 2. Run the test: dirsrvtests/tests/suites/tls/tls_check_crl_test.py 3. It will fail because it can't bind through ldaps. ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server", 'errno': 107, 'info': 'Transport endpoint is not connected'}
With CONFIG errorlog-level enabled: [12/Mar/2018:12:23:44.399132831 -0400] - WARN - Security Initialization - SSL alert: Unable to create PinObj (Netscape Portable Runtime error 0 - no error) [12/Mar/2018:12:23:44.399871405 -0400] - ERR - force_to_disable_security - ERROR: SSL Initialization Failed. Disabling SSL.
Additional info: If I build without srvcore merge commit: https://pagure.io/389-ds-base/c/e6cc278009192926d1fe0e9a87c8d69047dbdb7f?branch=master The test passes.
Metadata Update from @firstyear: - Issue assigned to firstyear
Interesting. I wonder if this is a dlopen issue? I'll look into this asap.
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
The change makes the test pass. Please, suggest if there is a saner way to fix this. More of a cleanup regarding old svrcore build system should be done I guess but better in a new ticket.
ack, and yes please open a ticket and describe what needs to be done. Thanks Matus!
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: None)
The test passes. Ack from me too :)
5bfe2a3e3..a3d3e1a93 master -> master
Metadata Update from @mhonek: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Great work! Can't believe it was such a simple fix :)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2660
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)