You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On occasion, some of our tests that use this Docker image fail due to a race condition that exists in the /etc/cont-init.d/050-openldap-populate script. This condition is somewhat rare, but it does contribute to failures in some of our most flaky tests.
What's Going On
In the 050-openldap-populate script (referred to as SCRIPT from here on in), the LDAP server is started with the slapd -h "ldapi:///" -u openldap -g openldap command and then the configure_msad_features function is invoked. That function contains an echo statement and then executes this command: ldapmodify -Y EXTERNAL -H ldapi:/// -f ${CONFIG_DIR}/msad.ldif -Q. On some occasions, where presumably the GitHub runners that we are using are overloaded, we can capture this output from the Docker container running this image:
The logs suggest that the ldapmodify command began executing before the LDAP server was ready to accept connections. Furthermore, because the e option is set in this Bash script, the failure of the ldapmodify command causes an immediate exit of the script, which leaves the LDAP server running and causes the endless loop of restarts of the slapd service.
The text was updated successfully, but these errors were encountered:
On occasion, some of our tests that use this Docker image fail due to a race condition that exists in the
/etc/cont-init.d/050-openldap-populate
script. This condition is somewhat rare, but it does contribute to failures in some of our most flaky tests.What's Going On
In the 050-openldap-populate script (referred to as SCRIPT from here on in), the LDAP server is started with the
slapd -h "ldapi:///" -u openldap -g openldap
command and then the configure_msad_features function is invoked. That function contains an echo statement and then executes this command:ldapmodify -Y EXTERNAL -H ldapi:/// -f ${CONFIG_DIR}/msad.ldif -Q
. On some occasions, where presumably the GitHub runners that we are using are overloaded, we can capture this output from the Docker container running this image:The logs suggest that the ldapmodify command began executing before the LDAP server was ready to accept connections. Furthermore, because the
e
option is set in this Bash script, the failure of the ldapmodify command causes an immediate exit of the script, which leaves the LDAP server running and causes the endless loop of restarts of the slapd service.The text was updated successfully, but these errors were encountered: