I don't think global requirements is the problem here. It would appear that this is also an issue in master. Since pyldap is an optional dependency that is managed in setup.cfg, we'll need to bump it there [0]. Then we can discuss the process for backporting this to stable/pike with the stable maintenance team.
I don't think global requirements is the problem here. It would appear that this is also an issue in master. Since pyldap is an optional dependency that is managed in setup.cfg, we'll need to bump it there [0]. Then we can discuss the process for backporting this to stable/pike with the stable maintenance team.
[0] https:/ /github. com/openstack/ keystone/ blob/fbce49970c b005986f5e49158 3c07bb3644355b0 /setup. cfg#L27