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

Puppet run continues despite failed Pluginsync

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: PUP 3.4.3
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      RHEL6

      Description

      A puppet run that has enough custom types/providers/facts to sync to a local system that it exceeds configtimeout (default 2m), should not continue to perform a puppet run, but rather completely fail. This would be the only way to meet the expectation that pluginsync ensures certain types/providers/facts are available before a module's code runs.

      If a puppetrun can continue despite failing to download plugins or custom facts, the proper operation of puppet modules cannot be guaranteed (without sanity checks in the puppet code). Also, it becomes impossible to base a Hiera hierarchy off of a custom fact because the first run would fail to pull in the expected Hiera data.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                wvl0 William Leese
              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support