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

`puppet resource user` does not work on Windows French edition

    Details

    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      * `puppet resource group` or `puppet resource user` could previously fail on non-English editions of Windows when there were users or groups present containing Unicode characters. This commonly occurred on the French localized edition of Windows where the "Guest" account is localized as "Invité"
      Show
      * `puppet resource group` or `puppet resource user` could previously fail on non-English editions of Windows when there were users or groups present containing Unicode characters. This commonly occurred on the French localized edition of Windows where the "Guest" account is localized as "Invité"

      Description

      Some basic functionality appears to be broken on a default French Windows that uses code page 850 by default. This uncovered two errors within Puppets logging and output emission at the console - Puppet is trying to use / combine incompatible strings in CP850 and UTF-8.

      Note that the problem only impacts puppet resource user and not puppet resource group - so some investigation should be done to fully understand the problem since those should behave similarly. Note also that no other puppet resource commands have been tested.

      This was discovered while attempting to replicate PUP-5938 - the first attempt to use puppet resource user also failed on Puppet 4.3.0, but with a different error. Not sure if it's worth investing any time in understanding that issue as well.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                erick Erick Banks
                Reporter:
                ethan Ethan Brown
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support