Issue #13397 has been updated by Chris Price. Target version changed from 2.7.13 to 2.7.x
---------------------------------------- Bug #13397: Puppet 2.7.12 not handling multiple versions of installed gems properly https://projects.puppetlabs.com/issues/13397#change-59582 Author: Wade Minter Status: In Topic Branch Pending Review Priority: Normal Assignee: Chris Price Category: Target version: 2.7.x Affected Puppet version: 2.7.12 Keywords: array, ruby, gems Branch: https://github.com/puppetlabs/puppet/pull/614 I just upgraded from Puppet 2.7.9 to 2.7.12, and am seeing something odd with regards to gem management. On our systems, we have multiple versions of gems installed: root@resque2:~# gem search -l libshadow *** LOCAL GEMS *** libshadow (1.0.0, 0.0.2) root@resque2:~# gem search -l god *** LOCAL GEMS *** god (0.12.1, 0.12.0, 0.11.0) However, when puppet runs, it appears to be concatenating the array of all of those versions together to build a string when comparing the installed versions to the desired target version: root@resque2:~# puppet agent --test info: Caching catalog for resque2.teamsnap.com info: Applying configuration version '1332685435' notice: /Stage[main]//Package[libshadow]/ensure: ensure changed '1.0.00.0.2' to '1.0.0' notice: /Stage[main]/Teamsnap_resque_worker::Package/Package[god]/ensure: ensure changed '0.12.10.12.00.11.0' to '0.12.1' notice: Finished catalog run in 12.35 seconds This seems to be incorrect behavior. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
