You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When you change the time specification in a cron.present entry from regular to special or vice versa, it will add the new job but not remove the old one. That results in two jobs with the same name,identifier, and user but different timespecs.
Setup
Please be as specific as possible and give set-up details.
on-prem machine
VM (Virtualbox, KVM, etc. please specify)
VM running on a cloud service, please be explicit and add details
container (Kubernetes, Docker, containerd, etc. please specify)
or a combination, please be explicit
jails if it is FreeBSD
Steps to Reproduce the behavior
Create a state like this in Pillar:
Description
When you change the time specification in a cron.present entry from regular to special or vice versa, it will add the new job but not remove the old one. That results in two jobs with the same name,identifier, and user but different timespecs.
Setup
Please be as specific as possible and give set-up details.
Steps to Reproduce the behavior
Create a state like this in Pillar:
apply state, then change the pillar to this:
Apply state again. There will now be two cron jobs in the crontab, that look like this:
Expected behavior
cron.present should delete the old
* * * * * pwd
entry when it creates the new@hourly pwd
one.Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)The text was updated successfully, but these errors were encountered: