Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

when changing from NOOP to OP old cronjob is not deleted #41

Closed
Phil-Friderici opened this issue Nov 18, 2013 · 3 comments
Closed

when changing from NOOP to OP old cronjob is not deleted #41

Phil-Friderici opened this issue Nov 18, 2013 · 3 comments

Comments

@Phil-Friderici
Copy link
Contributor

Changing an existing node from NOOP to OP will leave the OP reboot job in crontab.
One line/job for each time you change from NOOP to OP.
This can cleary lead to very unexpected results ;)
@Phil-Friderici
Copy link
Contributor Author

Instead changing the command from NOOP to OP, Puppet removes the comment line "# Puppet Name: puppet_agent_once_at_boot" and leaves the command as is.
Next parameter change will add an additional "puppet_agent_once_at_boot" job.

@Phil-Friderici
Copy link
Contributor Author

Found a ugly workaround for this. Will try to make it more readable before I send a PR.

@Phil-Friderici Phil-Friderici mentioned this issue Nov 19, 2013
Closed
@Phil-Friderici
Copy link
Contributor Author

never mind, not a daily business problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixing unremoved cronjobs, Issue #41
1 participant
@Phil-Friderici