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

URI.unescape mangles UTF-8 paths producing invalid ASCII strings

    XMLWordPrintable

Details

      • Existing test suites pass
      • May need additional acceptance tests to handle edge cases
      • Test cases should include puppet apply as well as puppet server.
    • Agent
    • 5
    • Agent 2017-04-05, Agent 2017-04-19, Agent 2017-05-03, Agent 2017-05-31, Agent 2017-06-14
    • Reviewed
    • Bug Fix
    • In some scenarios puppet could fail to manage file resources with UTF-8 file names because of incorrect character encoding and escaping when transforming requests into URI-compatible text. This is resolved in puppet 4.10.2 and 5.0.0.
    • No Action
    • Tested in spec

    Description

      Hi,

      I am running a puppet server under Ubuntu 12.04 (Puppet 2.7.11) and a puppet client under Ubuntu 14.04 (Puppet 3.4.2).

      I am distributing a directory of ttf fonts from the server to the clients, the rule is

      file

      {"/usr/local/share/fonts/FreeFonts": ensure => directory, mode => 0444, recurse => true, purge => true, source => "puppet:///modules/hadmut/soft/Daten/Fonts/Installation/FreeFonts", }

      This works with a great number of font files, but fails with one particular font:

      Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
      Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
      Wrapped exception:
      invalid byte sequence in US-ASCII
      Error: /Stage[main]/Hadmut::Application::X11_common/File[/usr/local/share/fonts/FreeFonts/Momоt___.ttf]/ensure: change from absent to file failed: Could not set 'file' on ensure: invalid byte sequence in US-ASCII

      For some reason Puppet assumes that this is an US-ASCII text file, but it should treat this as a binary.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. ENTERPRISE-758 File resource reports invalid byte sequence in US-ASCII for chinese character filename

          • Major - Major loss of function.
          • Open
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. PUP-6329 puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-2700 Puppet 3.6.1 File recurse improperly handles spaces in filenames

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. PUP-7658 Puppet 4.10.2 fails when Facter facts contains ampersand

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-1954 Puppet Server incorrectly handling URI decoding

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. PUP-3135 Square brackets in file names not handled properly

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Accepted

          Bug - A problem which impairs or prevents the functions of the product. PUP-7665 Puppet 5 fails when facter facts contain ampersands

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          links to

          Web Link Ubuntu Launchpad bug

          Activity

            People

              Unassigned Unassigned
              hadmut Hadmut Danisch
              Erik Dasher Erik Dasher
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support