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

Many puppet commands fail when using a configured or requested directory environment that doesn't exist.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • PUP 3.5.1 RC
    • PUP 3.7.0
    • Modules
    • None
    • 3
    • Week 2014-5-7 to 2014-5-14, Week 2014-5-14 to 2014-5-21

    Description

      This original description is documenting the difference between an agent making a request for an environment that does not exist, and an agent making a request for an environment that does not exist which also happens to be the configured environment on the master.

      On rhel6 vms, with a master puppet.conf of:

      [main]
          # The Puppet log directory.
          # The default value is '$vardir/log'.
          logdir = /var/log/puppet
       
          # Where Puppet PID files are kept.
          # The default value is '$vardir/run'.
          rundir = /var/run/puppet
       
          # Where SSL certificates are kept.
          # The default value is '$confdir/ssl'.
          ssldir = $vardir/ssl
       
          environmentpath = $confdir/environments
       
      [agent]
          # The file in which puppetd stores a list of the classes
          # associated with the retrieved configuratiion.  Can be loaded in
          # the separate ``puppet`` executable using the ``--loadclasses``
          # option.
          # The default value is '$confdir/classes.txt'.
          classfile = $vardir/classes.txt
       
          # Where puppetd caches the local configuration.  An
          # extension indicating the cache format is added automatically.
          # The default value is '$confdir/localconfig'.
          localconfig = $vardir/localconfig
          server = k2jv2z7f3vrqsoj.delivery.puppetlabs.net
      

      and environments:

      [root@k2jv2z7f3vrqsoj puppet]# tree /etc/puppet/environments/
      /etc/puppet/environments/
      └── foo
       
      1 directory, 0 files
      

      This agent call produces:

      [root@ueu8qnql450gx07 ~]# puppet agent -t --environment doesnotexist
      Info: Retrieving pluginfacts
      Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment doesnotexist source(s) puppet://k2jv2z7f3vrqsoj.delivery.puppetlabs.net/pluginfacts
      Info: Retrieving plugin
      Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment doesnotexist source(s) puppet://k2jv2z7f3vrqsoj.delivery.puppetlabs.net/plugins
      Warning: Not using cache on failed catalog
      Error: Could not retrieve catalog; skipping run
      

      And this one:

      [root@ueu8qnql450gx07 ~]# puppet agent -t --environment production
      Info: Retrieving pluginfacts
      Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://k2jv2z7f3vrqsoj.delivery.puppetlabs.net/pluginfacts
      Info: Retrieving plugin
      Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://k2jv2z7f3vrqsoj.delivery.puppetlabs.net/plugins
      Info: Caching catalog for ueu8qnql450gx07.delivery.puppetlabs.net
      Info: Applying configuration version '1397175258'
      Notice: Finished catalog run in 0.03 seconds
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              joshua.partlow Joshua Partlow
              Kurt Wall Kurt Wall
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support