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

Cached catalogs settings are ignored if noop is set to true

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.10.11, PUP 5.3.5, PUP 5.4.0
    • Component/s: None
    • Labels:
      None
    • Template:
      PUP Bug Template
    • Sub-team:
    • Team:
      Platform Core
    • Sprint:
      Platform Core KANBAN
    • Method Found:
      Needs Assessment
    • CS Priority:
      Reviewed
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Cached catalogs can now be used in --noop puppet apply & agent runs. The cached catalog will not be updated if one already exists, and a cached catalog not be created if there was no previously cached catalog.
    • QA Risk Assessment:
      No Action

      Description

      When using the following configuration options together:

      [agent]
      use_cached_catalog = true
      noop = true
      

      Cached catalogs settings are ignored and a new catalog is compiled every run. It is desirable to use both of these items together if you are controlling the rollout of changes (cached catalogs) and having to do so during change windows (noop); but still want the ability to remediate drift against the original catalog (cached catalogs; `puppet agent -t`).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jacob.helwig Jacob Helwig
              Reporter:
              matthew.cadorette Matthew Cadorette
              Votes:
              6 Vote for this issue
              Watchers:
              18 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support