Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-14642

OpenIDM status change to ACTIVE_NOT_READY due to scheduler bouncing intermittently.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 7.0.0
    • Fix Version/s: 7.1.0
    • Component/s: None
    • Labels:
    • Target Version/s:
    • Story Points:
      1
    • Sprint:
      2021.1 - IDM

      Description

      OpenIDM changes its status while ready to ACTIVE_NOT_READY due to the scheduler bouncing.

      This causes intermittent failures among the Jenkins run jobs.

      Example Suite:

       

      ./run-pybot.py --suite internal_objects openidm
      

      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.

      Test Structure:

      • 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

       

        Attachments

          Activity

            People

            • Assignee:
              cgdrake Chris Drake
              Reporter:
              brayden.roth-white Brayden Roth-White
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: