Roles migration job fails, and mod-roles-keycloak (v1.4.6) shows the following in logs:

[821739/mod-roles-keycloak] [mod-roles-keycloak] WARN   MigrationService     Permission migration was failed: jobId = f6f237a3-a3f8-4491-8fbf-465cc20a08f1

java.util.concurrent.CompletionException: jakarta.persistence.EntityNotFoundException: Keycloak resource is not found by static path: /circulation-item/{itemId}

Caused by: jakarta.persistence.EntityNotFoundException: Keycloak resource is not found by static path: /circulation-item/{itemId}

Scope:

1. If mod-roles-keycloak have some of pre-existing resources like capabilities or capabilities sets in place, then the migration will fail – this should be handled inside the code somehow in order not to throw errors during the migration;

2. If roles already exist in the cluster for some reason, they will not be created in mod-roles-keycloak through the API;

3. We are getting a large error message, it includes all the permissions not been added to the faulty role – would be great if these permission can be excluded somehow;

4. If there is any info about the root cause of the role not created, they are located at the debug loglevel, hence not displayed in CW logs, for example