Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-1877

Cron resource returns succesfully if the user is not cron allowed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 3.4.3
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
    • Environment:

      Red Hat Enterprise Linux Server release 6.5 (Santiago)
      Puppet 3.4.3

    • Template:

      Description

      The following Puppet code:

      cron { "somejob" :
      ensure => "present",
      command => "${data["directory"]}/epic_backup.sh > /var/log/epic_backup.log 2>&1",
      user => "pim",
      hour => [6],
      minute => [0],
      weekday => "0-7"
      }

      The /etc/cron.allow file:
      root

      The /etc/cron.deny file is empty

      Problem:
      puppet reports that it has succesfully created the cronjob, but can't be found on the system (crontab -u pim -l). This happens every puppet run, until the cronjob user has changed which is allowed to have cronjobs.

        Attachments

          Activity

            People

            • Assignee:
              kylo Kylo Ginsberg
              Reporter:
              pimpolderman Pim Polderman
              QA Contact:
              Narmadha Perumal
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support