This is the first testing call for OpenLDAP 2.6.2. Depending on the results, this may be the only testing call.
Generally, get the code for RE26:
Extract, configure, and build.
Execute the test suite (via make test) after it is built. Optionally, cd tests && make its to run through the regression suite.
Thanks!
OpenLDAP 2.6.2 Engineering Added libldap support for OpenSSL 3.0 (ITS#9436) Added slapd support for OpenSSL 3.0 (ITS#9436) Fixed ldapdelete to prune LDAP subentries (ITS#9737) Fixed libldap to drop connection when non-LDAP data is received (ITS#9803) Fixed libldap to allow newlines at end of included file (ITS#9811) Fixed slapd slaptest conversion of olcLastBind (ITS#9808) Fixed slapd to correctly init global_host earlier (ITS#9787) Fixed slapd bconfig locking for cn=config replication (ITS#9584) Fixed slapd usage of thread local counters (ITS#9789) Fixed slapd to clear runqueue task correctly (ITS#9785) Fixed slapd syncrepl handling of new sessions (ITS#9584) Fixed slapd to clear connections on bind (ITS#9799) Fixed slapd syncrepl ODSEE replication of unknown attr (ITS#9801) Fixed slapd-asyncmeta memory leak in keepalive setting (ITS#9802) Fixed slapd-ldap memory leak in keepalive setting (ITS#9802) Fixed slapd-meta SEGV on config rewrite (ITS#9802) Fixed slapd-meta ordering on config rewrite (ITS#9802) Fixed slapd-meta memory leak in keepalive setting (ITS#9802) Fixed slapd-monitor SEGV on shutdown (ITS#9809) Added slapo-autoca support for OpenSSL 3.0 (ITS#9436) Added slapo-otp support for OpenSSL 3.0 (ITS#9436) Fixed slapo-pcache SEGV on shutdown (ITS#9809) Fixed slapo-ppolicy operation handling to be consistent (ITS#9794) Build Enviornment Add ability to override default compile time paths (ITS#9675) Fix compiliation with certain versions of gcc (ITS#9790) Fix compilation with openssl exclusions (ITS#9791) Fix warnings from make jobserver (ITS#9788) Documentation admin26 Document new lloadd features (ITS#9780) Fixed slapd.conf(5)/slapd-config(5) syncrepl sizelimit/timelimit documentation (ITS#9804) Fixed slapd-sock(5) to clarify "sockresps result" behavior (ITS#8255)
Regards, Quanah
On 3/22/22 18:21, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.2.
Tested git revision 475e57281bc10e56a47021895a7b926e29ac9072 on openSUSE Tumbleweed x64_64 (gcc version 11.2.1):
- make test worked - unit tests of my Python module ldap0 work
Ciao, Michael.
El día martes, marzo 22, 2022 a las 10:21:07 -0700, Quanah Gibson-Mount escribió:
This is the first testing call for OpenLDAP 2.6.2. Depending on the results, this may be the only testing call.
Generally, get the code for RE26:
Extract, configure, and build.
Execute the test suite (via make test) after it is built. Optionally, cd tests && make its to run through the regression suite.
This is on SUSE Linux Enterprise Server 15 SP3.
$ export LD_LIBRARY_PATH=/usr/local/lib64 # for libsasl2.so 2.1.28
$ ./configure --enable-aci=yes --enable-dynacl --enable-spasswd=yes --enable-crypt=yes --enable-debug=yes --enable-shared=yes --enable-modules=yes --enable-slapi --enable-slapd=yes --with-tls --prefix=/opt/openldap-OPENLDAP_REL_ENG_2_6 $ make depend $ make $ make test
All fine.
matthias
On Tue, Mar 22, 2022 at 08:03:35PM +0100, Michael Ströder wrote:
On 3/22/22 18:21, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.2.
Tested git revision 475e57281bc10e56a47021895a7b926e29ac9072 on openSUSE Tumbleweed x64_64 (gcc version 11.2.1):
- make test worked
- unit tests of my Python module ldap0 work
Just a thought, are people pushing the RC code into testing/pre-prod environments? If so, would you be willing to share your results (pass/pass with concerns/fail, any relevant metrics you think might be of interest). Does the current schedule of 1+ weeks between a testing call and potential release give you enough time?
Thanks,
On 3/23/22 12:19, Ondřej Kuzník wrote:
On Tue, Mar 22, 2022 at 08:03:35PM +0100, Michael Ströder wrote:
On 3/22/22 18:21, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.2.
Tested git revision 475e57281bc10e56a47021895a7b926e29ac9072 on openSUSE Tumbleweed x64_64 (gcc version 11.2.1):
- make test worked
- unit tests of my Python module ldap0 work
Just a thought, are people pushing the RC code into testing/pre-prod environments?
Sometimes I do on my openSUSE-based Æ-DIR test systems based on branches of my packages in OBS. But it's additional work for which I don't always have spare time left.
Do you have any particular things in mind that need more thorough testing before 2.6.2 is released?
Does the current schedule of 1+ weeks between a testing call and potential release give you enough time?
IMHO most people are not going to test in real environments before the OpenLDAP project cuts a release, no matter how long this testing period is.
=> Release early, release often.
Ciao, Michael.
On Wed, Mar 23, 2022 at 03:07:25PM +0100, Michael Ströder wrote:
On 3/23/22 12:19, Ondřej Kuzník wrote:
On Tue, Mar 22, 2022 at 08:03:35PM +0100, Michael Ströder wrote:
On 3/22/22 18:21, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.2.
Tested git revision 475e57281bc10e56a47021895a7b926e29ac9072 on openSUSE Tumbleweed x64_64 (gcc version 11.2.1):
- make test worked
- unit tests of my Python module ldap0 work
Just a thought, are people pushing the RC code into testing/pre-prod environments?
Sometimes I do on my openSUSE-based Æ-DIR test systems based on branches of my packages in OBS. But it's additional work for which I don't always have spare time left.
Hi Michael, thanks, even that's appreciated.
Do you have any particular things in mind that need more thorough testing before 2.6.2 is released?
It was a general question. While it's nice that people run "make test" and sometimes "make its", it would be even nicer if we got regular feedback from actual test environments. If we got people to publish any metrics they gather (performance or otherwise), we could even track the evolution of the software in a real world setting, I know I'm not asking for much ;)
Does the current schedule of 1+ weeks between a testing call and potential release give you enough time?
IMHO most people are not going to test in real environments before the OpenLDAP project cuts a release, no matter how long this testing period is.
That has been a hypothesis for a while and this is an attempt to challenge it, just in case :)
Thanks,
Ondrej Kuzník ondra@mistotebe.net schrieb am 31.03.2022 um 17:55 in
Nachricht 20220331155558.GD26609@mistotebe.net:
On Wed, Mar 23, 2022 at 03:07:25PM +0100, Michael Ströder wrote:
On 3/23/22 12:19, Ondřej Kuzník wrote:
On Tue, Mar 22, 2022 at 08:03:35PM +0100, Michael Ströder wrote:
On 3/22/22 18:21, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.2.
Tested git revision 475e57281bc10e56a47021895a7b926e29ac9072 on
openSUSE
Tumbleweed x64_64 (gcc version 11.2.1):
- make test worked
- unit tests of my Python module ldap0 work
Just a thought, are people pushing the RC code into testing/pre-prod environments?
Sometimes I do on my openSUSE-based Æ-DIR test systems based on branches
of
my packages in OBS. But it's additional work for which I don't always have spare time left.
Hi Michael, thanks, even that's appreciated.
Do you have any particular things in mind that need more thorough testing before 2.6.2 is released?
It was a general question. While it's nice that people run "make test" and sometimes "make its", it would be even nicer if we got regular feedback from actual test environments. If we got people to publish any metrics they gather (performance or otherwise), we could even track the evolution of the software in a real world setting, I know I'm not asking for much ;)
Maybe maintain an OVL for each release, where "OVL" means "Operating System Verification List" ;-) (The list of Operating System Releases where compilation and selftest succeeded)
Does the current schedule of 1+ weeks between a testing call and potential release give you enough time?
IMHO most people are not going to test in real environments before the OpenLDAP project cuts a release, no matter how long this testing period
is.
That has been a hypothesis for a while and this is an attempt to challenge it, just in case :)
Thanks,
-- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
Hi,
No compilation or running issue of OpenLDAP 2.6.2 for on these distributions:
- debian 10
- debian 11
- ubuntu 20
- centos 7
Regards,
David
Le 22/03/2022 à 18:21, Quanah Gibson-Mount a écrit :
This is the first testing call for OpenLDAP 2.6.2. Depending on the results, this may be the only testing call.
Generally, get the code for RE26:
Extract, configure, and build.
Execute the test suite (via make test) after it is built. Optionally, cd tests && make its to run through the regression suite.
Thanks!
OpenLDAP 2.6.2 Engineering Added libldap support for OpenSSL 3.0 (ITS#9436) Added slapd support for OpenSSL 3.0 (ITS#9436) Fixed ldapdelete to prune LDAP subentries (ITS#9737) Fixed libldap to drop connection when non-LDAP data is received (ITS#9803) Fixed libldap to allow newlines at end of included file (ITS#9811) Fixed slapd slaptest conversion of olcLastBind (ITS#9808) Fixed slapd to correctly init global_host earlier (ITS#9787) Fixed slapd bconfig locking for cn=config replication (ITS#9584) Fixed slapd usage of thread local counters (ITS#9789) Fixed slapd to clear runqueue task correctly (ITS#9785) Fixed slapd syncrepl handling of new sessions (ITS#9584) Fixed slapd to clear connections on bind (ITS#9799) Fixed slapd syncrepl ODSEE replication of unknown attr (ITS#9801) Fixed slapd-asyncmeta memory leak in keepalive setting (ITS#9802) Fixed slapd-ldap memory leak in keepalive setting (ITS#9802) Fixed slapd-meta SEGV on config rewrite (ITS#9802) Fixed slapd-meta ordering on config rewrite (ITS#9802) Fixed slapd-meta memory leak in keepalive setting (ITS#9802) Fixed slapd-monitor SEGV on shutdown (ITS#9809) Added slapo-autoca support for OpenSSL 3.0 (ITS#9436) Added slapo-otp support for OpenSSL 3.0 (ITS#9436) Fixed slapo-pcache SEGV on shutdown (ITS#9809) Fixed slapo-ppolicy operation handling to be consistent (ITS#9794) Build Enviornment Add ability to override default compile time paths (ITS#9675) Fix compiliation with certain versions of gcc (ITS#9790) Fix compilation with openssl exclusions (ITS#9791) Fix warnings from make jobserver (ITS#9788) Documentation admin26 Document new lloadd features (ITS#9780) Fixed slapd.conf(5)/slapd-config(5) syncrepl sizelimit/timelimit documentation (ITS#9804) Fixed slapd-sock(5) to clarify "sockresps result" behavior (ITS#8255)
Regards, Quanah
On Fri, Apr 01, 2022 at 11:03:43AM +0200, Ulrich Windl wrote:
On Wed, Mar 23, 2022 at 03:07:25PM +0100, Michael Ströder wrote:
Do you have any particular things in mind that need more thorough testing before 2.6.2 is released?
It was a general question. While it's nice that people run "make test" and sometimes "make its", it would be even nicer if we got regular feedback from actual test environments. If we got people to publish any metrics they gather (performance or otherwise), we could even track the evolution of the software in a real world setting, I know I'm not asking for much ;)
Maybe maintain an OVL for each release, where "OVL" means "Operating System Verification List" ;-) (The list of Operating System Releases where compilation and selftest succeeded)
I don't think that's too helpful, since getting people to run OpenLDAP's own self-tests has never been a problem in my view. It's running the software with a real-world configuration that never seems to get reported.
I know Shawn runs a few replication scenarios regularly. It would be nice to know if we could get others to consider running the release candidates in their own test or staging systems and what were the perceived issues to getting that going.
Regards,
Ondrej Kuzník ondra@mistotebe.net schrieb am 01.04.2022 um 11:23 in
Nachricht 20220401092310.GE26609@mistotebe.net:
On Fri, Apr 01, 2022 at 11:03:43AM +0200, Ulrich Windl wrote:
On Wed, Mar 23, 2022 at 03:07:25PM +0100, Michael Ströder wrote:
Do you have any particular things in mind that need more thorough
testing
before 2.6.2 is released?
It was a general question. While it's nice that people run "make test"
and
sometimes "make its", it would be even nicer if we got regular feedback from actual test environments. If we got people to publish any metrics they gather (performance or otherwise), we could even track the evolution of the software in a real world setting, I know I'm not asking for much ;)
Maybe maintain an OVL for each release, where "OVL" means "Operating
System
Verification List" ;-) (The list of Operating System Releases where compilation and selftest succeeded)
I don't think that's too helpful, since getting people to run OpenLDAP's own self-tests has never been a problem in my view. It's running the software with a real-world configuration that never seems to get reported.
I know Shawn runs a few replication scenarios regularly. It would be nice to know if we could get others to consider running the release candidates in their own test or staging systems and what were the perceived issues to getting that going.
I was thinking like "Qubes OS HCL" (Hardware Compatibility List) that is viewable on their website. Of course if your statement is "our software runs everywhere without any problems", then you don't need it ;-)
Regards, Ulrich
Regards,
-- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
openldap-technical@openldap.org
-
David Coutadeur -
Matthias Apitz -
Michael Ströder -
Ondřej Kuzník -
Quanah Gibson-Mount -
Ulrich Windl