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

Agent's node request fails if environment directory doesn't exist locally

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • PUP 5.3.4
    • PUP 5.3.5, PUP 5.4.0
    • None
    • PUP Bug Template
    • Coremunity
    • Platform Core KANBAN
    • Needs Assessment
    • 32809,34018
    • 2
    • Bug Fix
    • Puppet apply no longer attempt to enforce the server-side requirements around environment directories when retrieving its node information from the server. Previously, this check could cause multiple catalog retrievals for a single run.
    • Manual

    Description

      Hi there,

      our puppet-agent got upgraded from 5.3.3 to 5.3.4 on all of our servers (Debian 8, Debian 9) and some of them throw a Warning at the beginning of their puppetrun.

      Warning: Unable to fetch my node definition, but the agent run will continue:
      Warning: Could not intern from application/json: Could not find a directory environment named 'my_custom_env' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?
      

      "my_custom_env" is located on my puppetserver under "/opt" somewhere so I don't know where "/etc/puppetlabs/code/environments" is coming from. Have you encountered this warning before? Do you know how to fix this?

      best regards and thanks
      Sebastian

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sfinke Sebastian Finke
              Votes:
              4 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support