Comment 1 for bug 1593749

My colleagues ran into this issue yesterday and I think we tracked it down to a hardcoded method of retrieving the 'latest' for a pip package on old versions of the puppet agent. See this commit and line number at:

https://github.com/puppetlabs/puppet/commit/152299cc859fc74343c697841848086d4e41b6f8#diff-41bbce95c82bdc373da03bb2f6116ef5L70

What we ended up doing was hardcoding the version of the pip packages in our package resource declarations that used the pip provider. We did this as a short-term workaround until we can upgrade Puppet to a newer version that did not have this hardcoded mechanism.