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

No option to fail fast when agent-specified environment does not exist

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • PUP 6.26.0, PUP 7.14.0
    • PUP 6.27.0, PUP 7.15.0
    • None
    • Monolithic
    • CentOS 7
    • Hide

      When using "strict_environment_mode=true", if the agent requests an environment that doesn't exist on the server, then the agent should fail the run without pluginsyncing or requesting a catalog. This is true for both server and agent specified environments.

      Previously the agent skipped pluginsync, requested a catalog, the server redirected the agent to "production" and the agent compared the catalog's environment with the environment it requested. If those were mismatched it failed the run, but it was "too late".

      Show
      When using "strict_environment_mode=true", if the agent requests an environment that doesn't exist on the server, then the agent should fail the run without pluginsyncing or requesting a catalog. This is true for both server and agent specified environments. Previously the agent skipped pluginsync, requested a catalog, the server redirected the agent to "production" and the agent compared the catalog's environment with the environment it requested. If those were mismatched it failed the run, but it was "too late".
    • Phoenix
    • 3
    • Phoenix 2022-03-02, Phoenix 2022-03-16
    • Needs Assessment
    • Bug Fix
    • When running in strict environment mode, we now fail the run early if the requested environment does not exist on the server or if the server does not allow the agent to specify it's own environment.
    • Needs Assessment

    Description

      Puppet Version:
      Puppet Server Version:
      OS Name/Version:

      Describe your issue in as much detail as possible…
      Describe steps to reproduce…

      Desired Behavior:

      Actual Behavior:

      Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.

      Examples:
      Run puppet agent with --test --trace --debug

      Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory.

      For more detailed information turn up the server logs by upping the log level in the server's logback.xml

      Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig)

      For memory issues with server heap dumps are also helpful.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              natemccurdy Nate McCurdy
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support