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

pip package provider does not handle pip executable paths with spaces

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 6.16.0, PUP 5.5.21
    • Component/s: None
    • Labels:
    • Template:
      PUP Bug Template
    • Team:
      Night's Watch
    • Story Points:
      2
    • Sprint:
      NW - 2020-05-13
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Paths containing spaces will now be quoted in pip package provider as it caused issues on Windows when executing CLI commands.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version: 6.4.5 and 6.14.0
      OS Name/Version: Windows

      On a Windows Server 2016 node running Puppet 6.4.5 and 6.14.0 with Python installed in a path with spaces, the Puppet catalog returns the below error if package collection is enabled:

      Cannot collect packages for Puppet::Type::Package::ProviderPip provider; [nil, nil]

      More specifically, this issue was fixed in PUP-9647 for getting the pip version, but this was not fixed when Puppet executes the `pip freeze -all' command to get the packages. 

      Desired Behavior:

      Quote function should be added to the pip provider here:
      https://github.com/puppetlabs/puppet/blob/6.14.0/lib/puppet/provider/package/pip.rb#L79

       

      Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig)

      For memory issues with server heap dumps are also helpful.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              luchian.nemes Luchian Nemes
              Reporter:
              tom.kishel Thomas Kishel
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support