Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
None
-
1
Description
Tests fail because the "setupLDAP" fails, in turn because (api.go:649)
NewRequest((*Client).PostJSON, "/settings/ldap/validate/connectivity", []byte(data.Encode()), status) |
returns
timeout: unexpected status code: request failed POST http://127.0.0.1:57096/settings/ldap/validate/connectivity 400 Bad Request: Invalid JSON |
This has happened in our 2.2 Jenkins builds for 7.0.0, and not for the 6.5.2 build that ran directly before it. It also failed on the 2.1 7.0.0 build, but not on the 2.1 6.5.2 build, so I can only assume this is an issue with 7.0.0. I've had a quick look around but I don't really know where I would look for details if something like this had been changed on the server end.
Note that the linked builds are for GKE, but the same is happening on EKS and AKS - it's also failing locally (on a kind cluster), which I just ran TestLDAPCreateAdminUser on to check, with log level 2. Attached the output - any other output you might want is available in the Jenkins job's Build Artifacts.
P.S. "7.0.0" above refers to 7.0.0-4390, and "6.5.2" to 6.5.2-6625 (the latest server weekly builds)
Attachments
Issue Links
- depends on
-
MB-44251 LDAP API Calls from Operator failing in 7.0.0
- Closed