Cron - Puppet not detecting 00 is the same as 0

asked 2018-03-27 06:23:05 -0500

Dear All,

I have created a cron manifest that is deploying a scheduled job successfully but I noticed that on some nodes the job was already in place. Puppet is adding a new entry even if the entry already existed in crontab. I have noticed that the minute field is being created by puppet as 0 as opposed to 00 hence it is not matching the existing rule. Can it be enforced so that puppet creates the entry as 00 ?

edit retag flag offensive close merge delete