Open Mstrodl opened 2 years ago
Can we revert this guy back to a working version of LDAP in the meantime, or should we move all our projects back to buster?
Oh wait, is this a problem with the Debian package?
Can we revert this guy back to a working version of LDAP in the meantime, or should we move all our projects back to buster?
Oh wait, is this a problem with the Debian package?
Bullseye ships libldap with a regression, and it's unlikely to be fixed because that's kinda their whole meme (:sparkles: stability :sparkles:)
It's fixed in newer libldap and older libldap (as in buster) doesn't have the issue
You may have luck with alpine or debian bookworm (unsure if python projects tend to build that or not... I'm not a doctor)
Something wonky happened between libldap
2.4.47
and2.4.59
that causes bullseye's libldap2.4.57
to give usSERVER_DOWN
errors when attempting to connect:This isn't great because we tend not to pin our container images to a particular release. We have a lot of things that have
python:3.9.7
instead ofpython:3.9.7-buster
. When these projects get rebuilt by OKD, stuff breaks because it can't talk to LDAP.