allow daemon jobs with underscores

Marwan Shaher Today at 12:15 PM
Grouper versions: 2.6.8 and 2.5.59
It looks like deleted daemon jobs, at least of type “Provisioning incremental sync” and “Provisioning full sync”, come back in an Enabled state if they were deleted using the daemon item menu, after the Grouper Daemon is restarted.
This happens even if the daemon job was in a Disabled state before it was deleted.
To make sure that the daemon jobs are actually deleted, the following parameters should be manually deleted from the configuration (grouper-loader.properties):
changeLog.consumer.MyProvisioner_Incremental.class
changeLog.consumer.MyProvisioner_Incremental.quartzCron
changeLog.consumer.MyProvisioner_Incremental.publisher.class
changeLog.consumer.MyProvisioner_Incremental.provisionerConfigId
changeLog.consumer.MyProvisioner_Incremental.publisher.debug
otherJob.MyProvisioner_Full.class
otherJob.MyProvisioner_Full.quartzCron
otherJob.MyProvisioner_Full.provisionerConfigId (edited)

4 replies

Justin Robinson 2 hours ago
We discovered that jobs with _ have some sticking power. See thread https://internet2.slack.com/archives/C7V0UQDJ4/p1642916707158600

Justin Robinson
I have a GSH daemon job that appears to be stuck in the system. I have tried to delete it, but when the daemon restarts it seems to bring it back into the system recreated. Any thoughts on how to purge it?
Thread in incommon-grouper | Jan 23rd | View message

Marwan Shaher 2 hours ago
Thanks! I’ll try it without underscores in the names as suggested in the thread

Marwan Shaher 2 hours ago
It was the underscores. Not having them in the daemon job name deletes the job as expected
:+1:
1

Justin Robinson 1 hour ago
On the other hand if you want a job to never go away - name it with an underscore consider it a fail safe