Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Stan Duffy updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Stan Duffy Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols assigned an issue to Unassigned Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Sprint: APS Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols assigned an issue to Kylo Ginsberg Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Assignee: Geoff Nichols Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Assignee: Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6699
Leading zero with cron resource is not handled as expected.
Change By:
Henrik Lindberg
Having a leading zero in the cron resource doesn't work as expected. It will either create a duplicate crontab entry or it is simply ignored.For example: {code:puppet} class crontest { cron { '/usr/local/bin/crontest.sh':ensure => 'present',command => '/usr/local/bin/crontest.sh',hour => ['06'],minute => ['30'],target => 'root',user => 'root', }} {code} {code} [root@pe-201621-master manifests]# crontab -l# Puppet Name: /usr/local/bin/crontest.sh30 6 * * * /usr/local/bin/crontest.sh {code} If your crontab entry already has a "non-Puppet" entry with a leading zero, it doesn't match it and creates a duplicate. For example: {code} [root@pe-201621-master manifests]# crontab -l30 06 * * * /usr/local/bin/crontest.sh {code} becomes... {code} [root@pe-201621-master manifests]# crontab -l30 06 * * * /usr/local/bin/crontest.sh# Puppet Name: /usr/local/bin/crontest.sh30 6 * * * /usr/local/bin/crontest.sh {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Henrik Lindberg Team: Agent & Platform Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Henrik Lindberg Component/s: Language Component/s: Types and Providers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title
Tim Purkerson created an issue
Puppet / PUP-6699
Leading zero with cron resource is not handled as expected.
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Unassigned
Components:
Language
Created:
2016/09/13 11:30 AM
Priority:
Normal
Reporter:
Tim Purkerson
Having a leading zero in the cron resource doesn't work as expected. It will either create a duplicate crontab entry or it is simply ignored.
For example:
class crontest { cron { '/usr/local/bin/crontest.sh': ensure => 'present', command => '/usr/local/bin/crontest.sh', hour => ['06'], minute => ['30'], target => 'root', user => 'root', }
}
[root@pe-201621-master manifests]# crontab -l
Puppet Name: /usr/local/bin/crontest.sh 30 6 * * * /usr/local/bin/crontest.sh
If your crontab entry already has a "non-Puppet" entry with a leading zero, it doesn't match it and creates a duplicate. For example:
