Uploaded image for project: 'Grouper'
  1. Grouper
  2. GRP-1902

With PSPNG, renaming a folder trigger a full sync

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 2.4.0.patch, 2.5.0, 2.4.1
    • provisioning
    • None

    Description

      Hello,

      I'm currently testing PSPNG with the lastest patche (21).
      During my tests, rename a folder (with some groups in it) triggered a full sync for all the provisioners :

      2018-09-10 13:57:00,594: [DefaultQuartzScheduler_Worker-1] INFO FullSyncProvisioner.queueAllGroupsForFullSync(551) -  - FullSyncer(pspng_attrFrEduLilHabilitation): Queuing all groups for full sync. (Work item invokes full sync: ProvisioningWorkItem[done=false,clog=clog #3931352 / ChangeLog type: stem: updateStem])
      2018-09-10 13:57:00,613: [DefaultQuartzScheduler_Worker-2] INFO FullSyncProvisioner.queueAllGroupsForFullSync(551) -  - FullSyncer(pspng_brancheListes): Queuing all groups for full sync. (Work item invokes full sync: ProvisioningWorkItem[done=false,clog=clog #3931352 / ChangeLog type: stem: updateStem])
      2018-09-10 13:57:02,047: [DefaultQuartzScheduler_Worker-3] INFO FullSyncProvisioner.queueAllGroupsForFullSync(551) -  - FullSyncer(pspng_brancheGrouper): Queuing all groups for full sync. (Work item invokes full sync: ProvisioningWorkItem[done=false,clog=clog #3931352 / ChangeLog type: stem: updateStem])

      Here the structure of the parent folder i renamed :
      app:test-pspng-du-10092018 ---> folder renamed
      – app:test-pspng-du-10092018:test-renommage
      – app:test-pspng-du-10092018:habil:test
      – app:test-pspng-du-10092018:habil:test10092018
      – app:test-pspng-du-10092018:habil:test-titi
      – app:test-pspng-du-10092018:habil:test-titi2

      So when i renamed the folder, just 2 provisioners should have been affected : pspng_attrFrEduLilHabilitation and pspng_brancheGrouper

      According to Bert :

      Therefore, editing a group's name would do an independent full-sync of that group in each of the provisioning targets the group was selected for.

      That's the problem, this is not the behavior I had : a full sync was started for all the provisioners and not only for the groups concerned but for all groups...(so it takes a lot of time...)

      If it can help, I attached an extract from my log when the full sync was triggered.

      Thanks for your help,
      Yoann

      Attachments

        Activity

          People

            bert.beelindgren@at.internet2.edu Bert Bee-Lindgren (gatech.edu)
            ydelattre2 Yoann Delattre (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Smart Checklist