Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-10101

scheduled_task : which_occurrence return empty value

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • None
    • scheduled_task
    • None
    • Needs Assessment

    Description

      Basic Info
      Module Version: 2.0.0
      Puppet Version: 6.10.1
      OS Name/Version: Windows Server 2019

      Describe your issue in as much detail as possible...

      Desired Behavior: which_occurrence should return the actual value like 'last'

      Actual Behavior: which_occurrence returns a empty string

      Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.

       

      Notice: /Stage[main]/Profile::Base/Scheduled_task[task]/trigger: trigger changed [
        {
          'start_date' => '2019-9-1',
          'start_time' => '05:40',
          'enabled' => true,
          'minutes_interval' => 0,
          'minutes_duration' => 0,
          'schedule' => 'monthly',
          'months' => [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12],
          'which_occurrence' => '',
          'day_of_week' => ['tues'],
          'index' => 0
        }] to [
        {
          'start_date' => '2019-9-1',
          'start_time' => '05:40',
          'minutes_interval' => 0,
          'minutes_duration' => 0,
          'schedule' => 'monthly',
          'months' => [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12],
          'which_occurrence' => 'last',
          'day_of_week' => ['tues']
        }] (corrective)
      Notice: Applied catalog in 14.33 seconds
      

      Attachments

        Issue Links

          Activity

            People

              ciaran.mccrisken Ciaran McCrisken
              aba-rechsteiner Benjamin Rechsteiner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support