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

changes in environment.conf does not trigger env cache eviction

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: PUP 3.7.5, PUP 4.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Puppet Developer Experience
    • Story Points:
      2

      Description

      If an environment.conf is changed, the changes does not take effect until that environment is evicted. This is esp. problematic when the environment.conf contains a timeout that is "unlimited" (a very long time to wait).

      Currently, there is a work around for this problem; the general settings can be touched, or the Puppet Server HTTP endpoint for cache eviction can be used to manually evict environment caches.

      Relates to PUP-5398 and PUP-5380.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              henrik.lindberg Henrik Lindberg
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support