Jira (PUP-10401) Pip package provider outputs warning on puppet run

[Nick Burgan (Jira)]

Nick Burgan created an issue

Puppet / PUP-10401 Pip package provider outputs warning on puppet run Issue Type: Bug Assignee: Unassigned Created: 2020/03/30 3:55 PM Priority: Normal Reporter: Nick Burgan Puppet Version: 6.14.0.135.gaf1499b7 (but may have started happening in earlier builds) Puppet Server Version: N/A, but using latest PE master build (rc2-37) OS Name/Version: centos 6, sles 12, ubuntu 18.04 When doing a puppet agent -t run, the following warnings are printed. /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: already initialized constant PIP_VERSION /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: previous definition of PIP_VERSION was here /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: already initialized constant PIP_VERSION_RANGE /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: previous definition of PIP_VERSION_RANGE was here This doesn't cause any errors, but is printed on every run. Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-10401

Re: Pip package provider outputs warning on puppet run I think the problem is the pip3 provider requires the parent class pip directly. Later the autoloader tries to load the pip provider which triggers the warning. Note the autoloader doesn't check to see if a file has already been loaded outside of the autoloader. Deleting this line seems to fix things: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/pip3.rb#L4

Add Comment

[Mihai Buzgau (Jira)]

Mihai Buzgau updated an issue

Puppet / PUP-10401

Pip package provider outputs warning on puppet run

Change By: Mihai Buzgau Sprint: PR - Triage

Add Comment

[Mihai Buzgau (Jira)]

Mihai Buzgau updated an issue

Puppet / PUP-10401 Pip package provider outputs warning on puppet run

Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-04-15

Add Comment

[Mihai Buzgau (Jira)]

Mihai Buzgau updated an issue

Puppet / PUP-10401 Pip package provider outputs warning on puppet run

Change By: Mihai Buzgau Story Points: 2

Add Comment

[Luchian Nemes (Jira)]

Luchian Nemes assigned an issue to Luchian Nemes

Puppet / PUP-10401 Pip package provider outputs warning on puppet run

Change By: Luchian Nemes Assignee: Luchian Nemes

Add Comment

[Gabriel Nagy (Jira)]

Gabriel Nagy updated an issue

Puppet / PUP-10401 Pip package provider outputs warning on puppet run

Change By: Gabriel Nagy Fix Version/s: PUP 6.15.0

Add Comment

[Claire Cadman (Jira)]

Claire Cadman updated an issue

Puppet / PUP-10401 Pip package provider outputs warning on puppet run

Change By: Claire Cadman Labels: doc_reviewed

Add Comment

[Tim Skirvin (Jira)]

Tim Skirvin commented on PUP-10401

Re: Pip package provider outputs warning on puppet run I'm still seeing this with puppet 6.17.0 on an RHEL7 system.

/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: already initialized constant PIP_VERSION /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: previous definition of PIP_VERSION was here /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: already initialized constant PIP_VERSION_RANGE /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: previous definition of PIP_VERSION_RANGE was here

Add Comment

[Tim Skirvin (Jira)]

Tim Skirvin updated an issue

Puppet / PUP-10401

Pip package provider outputs warning on puppet run

Change By: Tim Skirvin Comment:

I'm still seeing this with puppet 6.17.0 on an RHEL7 system. /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: already initialized constant PIP_VERSION /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: previous definition of PIP_VERSION was here /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: already initialized constant PIP_VERSION_RANGE /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: previous definition of PIP_VERSION_RANGE was here

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-10401

Re: Pip package provider outputs warning on puppet run Tim Skirvin can you see if any custom types/providers or facts are contributing to the issue: grep -r require /opt/puppetlabs/puppet/cache/lib

Add Comment

[Tim Skirvin (Jira)]

Tim Skirvin commented on PUP-10401

Re: Pip package provider outputs warning on puppet run

Indeed, that was it; I had written 'pip3.4' and 'pip3.6' providers for myself that were copies of the old 'pip' provider. I fixed my providers, the problem went away.

Add Comment

[Austin Boyd (Jira)]

Austin Boyd updated an issue

Puppet / PUP-10401

Pip package provider outputs warning on puppet run

Change By: Austin Boyd Labels: doc_reviewed jira_escalated

Add Comment

[Austin Boyd (Jira)]

Austin Boyd updated an issue

Puppet / PUP-10401 Pip package provider outputs warning on puppet run

Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 39907

Add Comment