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

Solaris Crontabs -> puppet resource cron only returns root account

    Details

    • Template:
      PUP Bug Template
    • Team:
      Night's Watch
    • Story Points:
      3
    • Sprint:
      PR - 2019-06-12, PR - 2019-06-25
    • Method Found:
      Needs Assessment
    • CS Priority:
      Reviewed
    • Zendesk Ticket IDs:
      34814
    • Zendesk Ticket Count:
      1
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Fixed reading of crontabs using Puppet for Solaris 11. Now crontabs for all users are listed when running 'puppet resource cron'
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version:2018.1.5
      Puppet Server Version:
      OS Name/Version: Solaris 11

      Unable to get a cron job from crontab for another user using `puppet resource cron` or `crontab -l` Solaris 11.

      This has been set with a .pp code through classification and it uses the `user` resource to set up the cron job. 

      Example :

      crontab -l -> returns only jobs in the root crontab file.

      crontab -l username -> returns only cron jobs in the users crontab.

      Puppet Resource Cron will only return the root crontab.

       

      Desired Behavior:

      When running a puppet resource cron it should return all crontabs

      Actual Behavior:

      Only the root accounts crontab is returned on Solaris 11.

       

      Cron is created with pp code
        cron

      { 'my cron job':                         command => "my command",                          user => "someuser",                 }

        Attachments

          Activity

            People

            • Assignee:
              sebastian.miclea Sebastian Miclea
              Reporter:
              jason.stewart Jason Stewart
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support