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

recon status may have incorrect data with recon after update

    Details

      Description

      The recon status may have processed number bigger than the total number in the resource, and different recon run may give different processed number with the exactly the same set of source and target data, here is one recon status from recon audit file:

      "f529d93d-f75a-4099-849b-be338bcd6b2a-42666","f529d93d-f75a-4099-849b-be338bcd6b2a-41308","2016-08-25T22:42:52.917Z","recon","openidm-admin",,,,,"systemLdapAccounts_managedUser","SOURCE_IGNORED: 0 UNQUALIFIED: 0 UNASSIGNED: 0 TARGET_IGNORED: 0 CONFIRMED: 604 AMBIGUOUS: 0 ABSENT: 0 MISSING: 0 FOUND_ALREADY_LINKED: 0 SOURCE_MISSING: 0 FOUND: 0 ","{""_id"":""f529d93d-f75a-4099-849b-be338bcd6b2a-41308"",""mapping"":""systemLdapAccounts_managedUser"",""state"":""SUCCESS"",""stage"":""COMPLETED_SUCCESS"",""stageDescription"":""reconciliation completed."",""progress"":{""source"":{""existing"":{""processed"":604,""total"":""600""}},""target"":{""existing"":{""processed"":604,""total"":""600""},""created"":0},""links"":{""existing"":{""processed"":604,""total"":""600""},""created"":0}},""situationSummary"":{""SOURCE_IGNORED"":0,""UNQUALIFIED"":0,""UNASSIGNED"":0,""TARGET_IGNORED"":0,""CONFIRMED"":604,""AMBIGUOUS"":0,""ABSENT"":0,""MISSING"":0,""FOUND_ALREADY_LINKED"":0,""SOURCE_MISSING"":0,""FOUND"":0},""statusSummary"":{""SUCCESS"":604,""FAILURE"":0},...""started"":""2016-08-25T22:42:37.231Z"",""ended"":""2016-08-25T22:42:52.916Z"",""duration"":15685}",,,"SUCCESS",,,,"recon","summary","f529d93d-f75a-4099-849b-be338bcd6b2a-41308"
      

      Notice that the total number of users in target/source is 600, but ""processed"" is 604.
      in another run, the processed can be 613 or 614.

      To reproduce:
      run QA Pyforge stress test
      python -u run-pybot.py -c stress -i gatling -s idm.ReconLDAPToManUser OpenIDM
      and check the recon audit file for recon update test.

      Note: Didn't see the same symptom with 3.1.0 and 4.0.0 release.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dhogan Dirk Hogan
                Reporter:
                Tinghua.Xu Tinghua.Xu
                QA Assignee:
                Tinghua.Xu
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: