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

Puppet Module List fails in code page 65001 on ja-JP windows

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:

      vmpooler win-2012r2-ja-x86_64
      beaker 2.52.0

    • Template:
    • Acceptance Criteria:
      Hide

      "puppet module list" should execute the same on codepage 65001 as it does on 932

      Show
      "puppet module list" should execute the same on codepage 65001 as it does on 932
    • Team:
      Coremunity
    • QA Risk Assessment:
      Automate

      Description

      Started a puppetlabs-dsc acceptance test run and RDP'd into the machine.
      Launched cmd and entered "> chcp 65001"
      then "puppet module list"

      Expect: a list of installed modules on the agent

      Actual:

      661 puppet/face/module/search.rb
        662 C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/terminal.rb
        663 puppet/face/module/uninstall.rb
        664 puppet/face/module/upgrade.rb
        665 C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/face/module.rb
       
      [NOTE]
      You may have encountered a bug in the Ruby interpreter or extension libraries.
      Bug reports are welcome.
      For details: http://www.ruby-lang.org/bugreport.html
       
       
      This application has requested the Runtime to terminate it in an unusual way.
      Please contact the application's support team for more information."
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              erick Erick Banks
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support