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

Don't backup to the local filebucket by default

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 7.0.0
    • Component/s: None
    • Template:
      PUP Bug Template
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Puppet will no longer backup files it overwrites or deletes by default to the local filebucket, since it will grow unbounded over time. The local filebucket can be re-enabled by setting `File { backup => 'puppet' }` as a resource default.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet agent's will backup any overwritten or deleted file to its local filebucket via the default backup parameter for the file type. It defaults to puppet which means to use the filebucket named puppet which is automatically created.

      Many users run into trouble because the filebucket will grow unbounded, such as PUP-1137. It has been proposed to use the tidy resource to clean up stale files, but can lead to memory issues with large numbers of file resources being created. See https://github.com/npwalker/pe_metric_curl_cron_jobs/issues/3

      For this ticket we should change the default value of the bucket parameter from puppet to false, see https://github.com/puppetlabs/puppet/blob/6.1.0/lib/puppet/type/file.rb#L110, and update the file reference documentation to reflect the new behavior.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              josh Josh Cooper
              Reporter:
              josh Josh Cooper
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support