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

Change default value of ignore_plugin_errors to false

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 7.0.0
    • Component/s: None
    • Template:
    • Team:
      Night's Watch
    • Story Points:
      1
    • Sprint:
      NW - 2020-09-01, NW - 2020-09-16, NW - 2020-09-30, NW - 2020-10-14
    • Release Notes:
      Enhancement
    • Release Notes Summary:
      Hide
      change default value of ignore_plugin_errors to false.

      If ignore_plugin_errors is true(default value before this commit),
      puppet agents can fail to pluginsync and will be missing facts/types/providers that may be needed to request and apply the catalog.

      For example, missing custom/external facts can change which classes are included in the catalog or cause compilation failures if the manifests references the missing fact.
      Show
      change default value of ignore_plugin_errors to false. If ignore_plugin_errors is true(default value before this commit), puppet agents can fail to pluginsync and will be missing facts/types/providers that may be needed to request and apply the catalog. For example, missing custom/external facts can change which classes are included in the catalog or cause compilation failures if the manifests references the missing fact.
    • QA Risk Assessment:
      Needs Assessment

      Description

      PUP-1763 added a setting to allow the agent to stop the run if pluginsync fails. In puppet 7, the setting should be changed so the agent should always fail the run if pluginsync fails.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ciprian.badescu Ciprian Badescu
              Reporter:
              josh Josh Cooper
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support