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

Puppet 3.6.1 File recurse improperly handles spaces in filenames

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • PUP 3.6.0
    • PUP 3.7.0
    • Types and Providers
    • None
    • Puppet 3.6.1 server, Puppet 3.6.1 client. Separate puppet server for catalog and puppet fileserver for this content, using passenger for both.

    • 2
    • Week 2014-6-4 to 2014-6-11, Week 2014-6-11 to 2014-6-18

    Description

      This one's new on me.
      We're using file{ : recurse => remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call.

      Here's a convenient, if ugly, example:

      In the Fileserver:

      [29/May/2014:14:15:18 -0700] "GET /production/file_content/puppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%2520template%2520(dev).cpython-34.pyc HTTP/1.1" 404 147 "-" "-"
      

      in the client:

      Error 404 on SERVER: Not Found: Could not find file_content puppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%20template%20(dev).cpython-34.pyc
      Error: /Stage[main]/.../File[/opt/python340/lib/python3.4/site-packages/setuptools/__pycache__/script template (dev).cpython-34.pyc]/ensure: change from absent to file failed:
      Could not set 'file' on ensure: 
      Error 404 on SERVER: Not Found: 
      Could not find file_content puppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%20template%20(dev).cpython-34.pyc
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dreamlibrarian Tristan Smith
              Narmadha Perumal Narmadha Perumal
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support