OpenIDM changes its status while ready to ACTIVE_NOT_READY due to the scheduler bouncing.
This causes intermittent failures among the Jenkins run jobs.
This is a top level suite that uses the same IDM instance for all test cases below it, and uses default configuration with no changes.
- Start IDM out of the box
- Wait for managed/user availability
- CRUD tests on internal objects (roles/users etc.)
Attached two log files:
- One from a run with a failure due to an endpoint not being available at the time of a read
- One from a run with no failures but the same ACTIVE_NOT_READY issue and a higher org.forgerock.openidm.health.HealthService.level logging level