PSPNG - Nested groups can cause ldapUser lookup error

PSPNG sometimes crashes when groups are added as members within other groups. For example, the following log occurs when
Group1 has a few members
Group1 is added to Group2
[Both Group1 & Group2 are selected for provisioning]

2016-10-03 16:51:55,311: [DefaultQuartzScheduler_Worker-6] INFO [pspng_epe] CLog/pspng_epe/start/ - - Fetching 4 users from target system

2016-10-03 16:51:55,317: [DefaultQuartzScheduler_Worker-6] INFO [pspng_epe] CLog/pspng_epe/start/ - - Read 3 user objects from directory

2016-10-03 16:51:55,317: [DefaultQuartzScheduler_Worker-6] WARN [pspng_epe] CLog/pspng_epe/start/ - - pspng_epe: User not found in target system: 2f7d73e5f93347bebd1cf70e426b127

3

2016-10-03 16:51:55,318: [DefaultQuartzScheduler_Worker-6] ERROR [pspng_epe] CLog/pspng_epe/prov/658// - - Problem provisioning item ProvisioningWorkItem[clog=clog #658 / ChangeL

og type: membership: addMembership]

edu.internet2.middleware.grouper.pspng.PspException: pspng_epe: LdapUser does not exist for subject 2f7d73e5f93347bebd1cf70e426b1273

at edu.internet2.middleware.grouper.pspng.LdapAttributeProvisioner.addMembership(LdapAttributeProvisioner.java:89)

at edu.internet2.middleware.grouper.pspng.LdapAttributeProvisioner.addMembership(LdapAttributeProvisioner.java:1)

at edu.internet2.middleware.grouper.pspng.Provisioner.provisionItem(Provisioner.java:888)

at edu.internet2.middleware.grouper.pspng.Provisioner.provisionBatchOfItems(Provisioner.java:1163)

at edu.internet2.middleware.grouper.pspng.PspChangelogConsumerShim.processChangeLogEntries(PspChangelogConsumerShim.java:71)

at edu.internet2.middleware.grouper.changeLog.ChangeLogHelper.processRecords(ChangeLogHelper.java:242)

at edu.internet2.middleware.grouper.app.loader.GrouperLoaderType$4.runJob(GrouperLoaderType.java:629)

at edu.internet2.middleware.grouper.app.loader.GrouperLoaderJob.runJob(GrouperLoaderJob.java:416)

at edu.internet2.middleware.grouper.app.loader.GrouperLoaderJob.execute(GrouperLoaderJob.java:318)

at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)

It looks like the nested group is being sought as a subject from the target ldap system.