Jira (PUP-10395) Gem provider reports changes when using composed requirements

Gheorghe Popescu (Jira)

unread,

Mar 27, 2020, 10:11:03 AM3/27/20

to puppe...@googlegroups.com

Gheorghe Popescu created an issue

Puppet /

PUP-10395

Gem provider reports changes when using composed requirements

Issue Type:	Task
Affects Versions:	PUP 5.5.18, PUP 6.14.0
Assignee:	Unassigned
Components:	Types and Providers
Created:	2020/03/27 7:10 AM
Priority:	Normal
Reporter:	Gheorghe Popescu

Puppet Version:
Puppet Server Version:
OS Name/Version:

Describe your issue in as much detail as possible…
Describe steps to reproduce…

Desired Behavior:

Actual Behavior:

Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.

Examples:
Run puppet agent with --test --trace --debug

Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory.

For more detailed information turn up the server logs by upping the log level in the server's logback.xml

Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig)

For memory issues with server heap dumps are also helpful.

Add Comment

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

Gheorghe Popescu (Jira)

unread,

Mar 27, 2020, 10:21:03 AM3/27/20

to puppe...@googlegroups.com

Gheorghe Popescu updated an issue

Puppet /

PUP-10395

Gem provider reports changes when using composed requirements

Change By:	Gheorghe Popescu

*Puppet Version: 5.5.x, master *
*Puppet Server Version:*
*OS Name/Version:*

Describe your issue When installing packages and using the gem provider, if you pass in as much detail as possible…
Describe steps to reproduce…

*Desired Behavior the ensure a composed requirement('>1, <2') puppet will always report changes : *

*Actual Behavior {code : *

Please take puppet}box# cat a moment and attach any relevant log output and/or manifests . This will help us immensely when troubleshooting the issue.

Examples pp
package { 'color' :
ensure => ">1, <2",
provider => "gem"
}
Run box# puppet agent with apply a.pp -- test detailed - exitcodes Notice: Compiled catalog for worse - trace --debug

Relevant sections of {{ swoop.delivery.puppetlabs.net in environment production in 0.41 seconds Notice: / var Stage[main] / log Main / puppetlabs Package[color] / puppetserver/puppetserver ensure: ensure changed ['1 . log}} or any applicable logs from the same directory 8', '0 .

For more detailed information turn up the server logs by upping the log level in the server 1.0 ' s logback ] to '>1, <2' Notice: Applied catalog in 0 . xml 66 seconds
box# echo $? 2

Relevant sections of configurations files ( box# puppet apply a . conf, hiera pp --detailed-exitcodes Notice: Compiled catalog for worse-swoop . conf delivery.puppetlabs.net in environment production in 0.41 seconds Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8' , Server ' s conf 0 . d 1.0'] to '>1 , defaults/sysconfig) <2' Notice: Applied catalog in 0.68 seconds
box# echo $? 2
{code}
For memory issues
Seems like the Gem::Dependecy.new(https://github.com/ruby/ruby/blob/master/lib/rubygems/dependency.rb#L39) accepts a sparse argument and it can be used with server heap dumps an array but we are also helpful sending a string(https://github . com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb#L130)

Add Comment

Gheorghe Popescu (Jira)

unread,

Mar 27, 2020, 10:22:03 AM3/27/20

to puppe...@googlegroups.com

Gheorghe Popescu updated an issue

Puppet /

PUP-10395

Gem provider reports changes when using composed requirements

Change By:	Gheorghe Popescu

*Puppet Version: 5.5.x, master*

When installing packages and using the gem provider, if you pass in the ensure a composed requirement('>1, <2') puppet will always report changes:
{code:puppet}box# cat a.pp

package { 'color':
ensure => ">1, <2",
provider => "gem"
}

box# puppet apply a.pp --detailed-exitcodes
Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 seconds
Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2'
Notice: Applied catalog in 0.66 seconds
box# echo $? 2

box# puppet apply a.pp --detailed-exitcodes
Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 seconds
Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2'

Notice: Applied catalog in 0.68 seconds
box# echo $? 2
{code}

Seems like the Gem::Dependecy.new(https://github.com/ruby/ruby/blob/master/lib/rubygems/dependency.rb#L39) accepts a sparse argument and it can be used with an array but we are sending a string(https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb#L130)

Add Comment

Gheorghe Popescu (Jira)

unread,

Mar 27, 2020, 10:22:04 AM3/27/20

to puppe...@googlegroups.com

Gheorghe Popescu (Jira)

unread,

Mar 27, 2020, 10:23:03 AM3/27/20

to puppe...@googlegroups.com

Gheorghe Popescu updated an issue

Puppet /

PUP-10395

Gem provider reports changes when using composed requirements

Change By:	Gheorghe Popescu
Acceptance Criteria:	I can use composed requirements(>x, <y) with the gem provider as the gem command provides this functionality

Add Comment

Gheorghe Popescu (Jira)

unread,

Mar 27, 2020, 10:23:04 AM3/27/20

to puppe...@googlegroups.com

Gheorghe Popescu updated an issue

Puppet /

PUP-10395

Gem provider reports changes when using composed requirements

Change By:	Gheorghe Popescu

*Puppet Version: 5.5.x, master*

When installing packages and using the gem provider, if you pass in the ensure a composed requirement('> 1 x , < 2 y ') puppet will always report changes:

{code:puppet}box# cat a.pp
package { 'color':
ensure => ">1, <2",
provider => "gem"
}
box# puppet apply a.pp --detailed-exitcodes
Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 seconds
Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2'
Notice: Applied catalog in 0.66 seconds
box# echo $? 2

box# puppet apply a.pp --detailed-exitcodes
Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 seconds
Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2'
Notice: Applied catalog in 0.68 seconds
box# echo $? 2
{code}

Seems like the Gem::Dependecy.new(https://github.com/ruby/ruby/blob/master/lib/rubygems/dependency.rb#L39) accepts a sparse argument and it can be used with an array but we are sending a string (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb#L130)