Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title
Josh Cooper commented on PUP-10394
Re: puppet cannot handle same package name with different providers
Ah I think this is a duplicate of two other bugs. The issue of puppet resource package hiding packages from multiple providers is PUP-7497. I left a note and potential patch in that ticket. The issue of multiple packages with the same name in a manifest is PUP-5302. Puppet requires the title to be unique, so you have to give it a dummy title and specify the name parameter separately:
[root@wild-enthusiast ~]# cat a.pp
package { 'uuid':
ensure => present,
provider => 'gem'
}
package { 'uuid':
ensure => present,
provider => 'yum'
}
[root@wild-enthusiast ~]# puppet apply a.pp
Error: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Package[uuid] is already declared at (file: /root/a.pp, line: 1); cannot redeclare (file: /root/a.pp, line: 6) (file: /root/a.pp, line: 6, column: 1) on node
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10394 puppet cannot handle same package name with different providers Change By: Bogdan Irimie Sprint: ready for triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351401.1585313546000.72430.1604566322318%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10394 puppet cannot handle same package name with different providers Change By: Bogdan Irimie Sprint: Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351401.1585313546000.72329.1604566200128%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Ciprian Badescu commented on PUP-10394 Re: puppet cannot handle same package name with different providers probably caused by: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/package.rb#L312 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351401.1585313546000.33268.1586338680655%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10394 puppet cannot handle same package name with different providers Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351401.1585313546000.25660.1585666380112%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title
Ciprian Badescu commented on PUP-10394
Re: puppet cannot handle same package name with different providers
And 6.14.0 seems to behave the same:
[root@ski-residence ~]# puppet --version
6.14.0
[root@ski-residence ~]# puppet apply b.pp
Error: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Package[postgresql] is already declared at (file: /root/b.pp, line: 1); cannot redeclare (file: /root/b.pp, line: 5) (file: /root/b.pp, line: 5, column: 1) on node ski-residence.delivery.puppetlabs.net
[root@ski-residence ~]# puppet resource package postgresql provider=dnf ensure=present
package { 'postgresql':
ensure => '12.1-2.module_el8.1.0+273+979c16e6',
provider => 'dnf',
}
[root@ski-residence ~]# puppet resource package postgresql provider=dnfmodule ensure=present
package { 'postgresql':
ensure => '12',
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title
Ciprian Badescu commented on PUP-10394
Re: puppet cannot handle same package name with different providers
On 5.5.x, having '--param provider' or specifying second provider in manifest does not seems to help:
[root@ski-residence ~]# cat b.pp
package { 'postgresql':
ensure => present,
provider => 'dnfmodule',
}
package { 'postgresql':
ensure => present,
provider => 'dnf',
}
[root@ski-residence ~]# puppet apply b.pp
Error: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Package[postgresql] is already declared at (file: /root/b.pp, line: 1); cannot redeclare (file: /root/b.pp, line: 5) (file: /root/b.pp, line: 5, column: 1) on node ski-residence.delivery.puppetlabs.net
[root@ski-residence ~]# puppet
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10394 puppet cannot handle same package name with different providers Change By: Josh Cooper Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351401.1585313546000.23184.1585345980133%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title
Josh Cooper commented on PUP-10394
Re: puppet cannot handle same package name with different providers
This issue should already be supported, see PUP-1073 In PUP-3721 (fixed in 6.13.0), puppet resource package now emits the provider that was used, to avoid naming collisions. You can achieve the same effect in 5.5.x using puppet resource package --param provider. In order to manage two packages with the same name, you have to specify the provider for both resources, which I think is why this fails:
root@sleek-clergymen:~# cat a.pp package { 'ssh-import-id': ensure => '3.21', provider => 'pip', } package { 'ssh-import-id': ensure => '3.21-0ubuntu1', }
I don't think puppet will generate the composite key for the resource if the provider is unspecified, and it picks the most suitable provider. See also https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/package/common_package_name_in_different_providers.rb
Add Comment
This message was sent by
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title
Ciprian Badescu created an issue
Puppet / PUP-10394
puppet cannot handle same package name with different providers
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2020/03/27 5:52 AM
Priority:
Normal
Reporter:
Ciprian Badescu
While testing package providers I hit the case on Ubuntu14.04/x86_64 where the same package is present on both apt and pip providers. While individually the packages can be handled, there are issues on:
output on `puppet resource package`, where only the default package gets listed
having both packages in the same manifest
root@sleek-clergymen:~# puppet resource package ssh-import-id ensure=present provider=pip
package { 'ssh-import-id':
ensure => '3.21',
}
root@sleek-clergymen:~# pip freeze | grep ssh-import-id
