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

Puppet resource broken when directory environments enabled

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.7.1, PUP 3.7.2
    • Fix Version/s: PUP 3.7.3
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      3
    • Sprint:
      Platform Server 2014-10-29, Platform Server 2014-11-12

      Description

      When running puppet resource, the command fails for want of a 'none' environment

      puppet resource file /usr/share/puppet-dashboard-mirror ensure=directory source=/usr/share/puppet-dashboard recurse=true ignore='log'
      Error: /File[/usr/share/puppet-dashboard-mirror]: Failed to generate additional resources using 'eval_generate': Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist?
      Error: /File[/usr/share/puppet-dashboard-mirror]: Could not evaluate: Could not retrieve file metadata for file:/usr/share/puppet-dashboard: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist?
      Wrapped exception:
      Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist?
      Error: Could not run: Could not retrieve file metadata for file:/usr/share/puppet-dashboard: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist?
      Wrapped exception:
      Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist?

      Note also - when a large number of directory environments exist, the valid_directories routine in /usr/lib/ruby/site_ruby/1.8/puppet/environments.rb takes a lot of time to stat the environment directory and work out whether all the directories are valid (I currently have 224 environments and the delay between e.g. a puppet agent -t --debug and the command even starting to display debug output is something like 10s (ymmv depending on IO etc)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                fiddyspence Chris Spence
                QA Contact:
                Eric Thompson
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support