The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #23122

'pkg' package provider does not understand IPS package versions properly

Added by Lauri Tirkkonen over 2 years ago. Updated over 2 years ago.

Status:UnreviewedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version:3.3.1 Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:

This ticket is now tracked at:


It would seem the ‘pkg’ provider (for illumos/Solaris/OpenSolaris IPS) does not do the right thing with IPS package versions. We’re running OmniOS and seeing this:

kekkonen ~ % pfexec puppet apply -e 'package {"mdb": ensure => latest }'
Notice: Compiled catalog for in environment production in 1.17 seconds
Notice: Finished catalog run in 6.39 seconds
kekkonen ~ % pfexec pkg update -nv mdb                                                  
            Packages to update:        1
     Estimated space available: 14.11 TB
Estimated space to be consumed: 24.61 MB
       Create boot environment:       No
Create backup boot environment:      Yes
          Rebuild boot archive:       No

Changed packages:
    0.5.11,5.11-0.151006:20130731T194820Z -> 0.5.11,5.11-0.151006:20131019T183740Z

So puppet thinks there are no updates, but pkg correctly notices that an update is available (only the timestamp has changed, not the version, build release, or branch numbers).

puppet resource provides some insight into this:

kekkonen ~ % puppet resource package mdb
package { 'mdb':
  ensure => '0.5.11-0.151006',

This version number is not correct, it’s missing the build release (5.11) and timestamp.


#1 Updated by Anonymous over 2 years ago

Redmine Issue #23122 has been migrated to JIRA:

Also available in: Atom PDF