-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Affects Version/s: COmanage Registry 3.3.1 (Magic Ring MR1)
-
Component/s: Registry Plugins
Clicked "Reprovision All" for the LDAP Provisioner. The queued job then ran via cron and recorded
https://registry.gw-astronomy.org/registry/co_jobs/view/4070
Job Type
|
Provisioner (23)
|
Job Parameters
|
{"co_provisioning_target_id":"23","record_type":"All"}
|
Job Mode
|
All
|
Status
|
Complete
|
Queued
|
Sat Nov 14 06:23:16 2020 America/Chicago
|
Register Summary
|
Started via JobShell by http://cilogon.org/serverT/users/64703 (CoPerson ID )
|
Started
|
Sat Nov 14 06:24:01 2020 America/Chicago
|
Start Summary
|
Reprovisioning target id 23 for record type All
|
Finished
|
Sat Nov 14 06:27:21 2020 America/Chicago
|
Finish Summary
|
Processed 403 record(s) (403 success, 0 error)
|
One of the specific Job History Records is
https://registry.gw-astronomy.org/registry/co_job_history_records/view/10688
Job
|
4070
|
Key
|
840
|
Comment
|
Provisioning completed successfully
|
Status
|
Complete
|
CO Person
|
Organizational Identity
|
Created
|
Sat Nov 14 06:24:27 2020 America/Chicago
|
|
An inspection of the LDAP record for the CO Person shows the LDAP record was not re-provisioned.
Running a re-provision synchronously for the CO Person record results in the LDAP record being immediately re-provisioned.