Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with Package defaults warning #122

Closed
zipkid opened this issue Sep 18, 2014 · 9 comments
Closed

Problem with Package defaults warning #122

zipkid opened this issue Sep 18, 2014 · 9 comments

Comments

@zipkid
Copy link
Member

zipkid commented Sep 18, 2014

as of puppet 3.6.1 there is a deprecation warning.
https://docs.puppetlabs.com/puppet/3.6/reference/release_notes.html#changes-to-rpm-behavior-with-virtual-packages

When using this puppet-python module setting this does not remove the warning as it should.

This is caused by the creation of a package resource in the 3 facts included in the module.
https://github.com/stankevich/puppet-python/blob/master/lib/facter/pip_version.rb#L4
pkg = Puppet::Type.type(:package).new(:name => "python-pip")

@neilkatin
Copy link

See also this ticket: https://tickets.puppetlabs.com/browse/PUP-2974, which seems to describe the same problem.

@shivapoudel
Copy link
Contributor

@neilkatin and @zipkid I have quiet busy schedule at the moment. Coming week I'll see what this issue is about :)

@KlavsKlavsen
Copy link
Contributor

just found that those two facts gives me the same warnings :(

@treydock
Copy link
Contributor

+1. Running Puppet 3.6.2 and Puppet apply (masterless nodes) all generate the warning.

@eshamow
Copy link
Contributor

eshamow commented Oct 23, 2014

+1 seeing this on 3.7.2.

@shivapoudel
Copy link
Contributor

@eshamow Thanks for this :)

@shivapoudel
Copy link
Contributor

Seems like we should mark this issue as solved. If anybody finds this as unsolved they please do report to open this issue :octocat:

@KlavsKlavsen
Copy link
Contributor

one note - this breaks puppet < 3.6 (since they do not have allow_virtual option.
in defaults.pp I check for puppetversion - before setting this, so that should be done here as well.

@eshamow
Copy link
Contributor

eshamow commented Nov 4, 2014

@KlavsKlavsen agreed - will look into this and file another PR to resolve - @shivapoudel we should probably re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants