Closed mhajas closed 1 week ago
The user is not present user-29
in realm-0
where the request is being sent. So I would say the errors are expected and we need to find and fix the dataset workflow, on why this is happening.
id | email | email_constraint | email_verified | enabled | federation_link | first_name | last_name | realm_id | username | created_timestamp | service_account_client_link | not_before
--------------------------------------+---------------------+---------------------+----------------+---------+-----------------+---------------+--------------+----------+----------+-------------------+-----------------------------+------------
312d91a7-fe1e-42c4-a9a8-87a6476d6cff | user-29@realm-1.com | user-29@realm-1.com | f | t | | user-29-first | user-29-last | realm-1 | user-29 | 1718266579257 | | 0
(1 row) ```
I had a look at the ExecutionHelper
in the dataset provider, and found that it might ignore exceptions in failed tasks. I'll create a PR.
Watching it for another night or two to see a possible root cause as that should now be logged.
Didn't occur again, closing. Will open a new issue if it reoccurs.
While looking into nightly run Gatling results from this run: https://github.com/keycloak/keycloak-benchmark/actions/runs/9493985920 I found out there is a small amount of errors for the Post correct credentials step.
The number of errors is small (140/91500), however, this is not expected. Keycloak should handle all requests. This is happening with all deployment flavours Active/Passive, Persistent sessions and Active/Active.
Here is a Gatling result for A/A:![image](https://github.com/keycloak/keycloak-benchmark/assets/13901995/f0365f57-cfc3-4201-9422-a795aa4311e8)
The error response is the following:
Here is the full request response from Gatling log: