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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593749 Title: puppet apply with pip provider gives 403 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1593749/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
