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.

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

Don't use --timestring when command is snapshot #60

Open
abo-adapt opened this issue Aug 31, 2015 · 3 comments
Open

Don't use --timestring when command is snapshot #60

abo-adapt opened this issue Aug 31, 2015 · 3 comments

Comments

@abo-adapt
Copy link

Currently snapshot cronjobs get --timestring added. This results in curator giving a warning that --timestring is used, but neither --newer-than nor --older-than is used. This prevents the command from actually executing through cron (at least on our servers). This simple patch fixes that:

--- a/modules/curator/manifests/job.pp
+++ b/modules/curator/manifests/job.pp
@@ -81,7 +81,11 @@ define curator::job (
$_regex = undef
}

  • $_timestring = "--timestring '${timestring}'"
  • if ($command == "snapshot") {
  • $_timestring = undef
  • } else {
  • $_timestring = "--timestring '${timestring}'"
  • }
@jlambert121
Copy link
Owner

What version of curator are you using?

@abo-adapt
Copy link
Author

$ curator --version
curator, version 3.3.0

The evenup/curator puppet module is version 2.1.1

@jlambert121
Copy link
Owner

It looks like my version of curator is a bit dated (3.0.2) which works fine. The timestring parameter is one I use on snapshots so I don't want to just remove it completely. Other thoughts on how to tackle this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants