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 #14088

Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest

Added by Mark Koch about 4 years ago. Updated over 2 years ago.

Status:AcceptedStart date:04/19/2012
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:

This ticket is now tracked at:


Puppet’s yum provider for the package resource does not appear to offer complete support for RPM naming/versioning.

Yum compares RPMs using the RPM naming convention (e.g name-version-release.arch.rpm). Our snapshot RPMs make use of this convention and rely upon the fact that yum can distinguish between RPMs based on the release components.

For example, in our yum snapshot repo we have;


When we run ‘yum install mds-2.0.1’, yum will select the rpm with release = SNAPSHOT20120418223400 as the latest version of mds-2.0.1.

When we attempt to use Puppet’s package resource to perform the same operation with

package { 'mds-2.0.1':
    ensure => latest

Puppet appears to use rpm to gather information about the local install but then does not compare the result to what the yum repo can provide (.i.e. compare release tags). Instead it simply ensures that an rpm with a matching name-version has been installed.

To workaround this issue we’re currently calling yum directly using,

exec { "install mds-${meter_data_service_version}":
    command => "yum -d 1 -e 1 install mds-${meter_data_service_version} -y",
    path    => "/usr/bin/",

This is functional but couples us to yum and is not recommended practice in Puppet.

Related issues

Related to Puppet - Bug #17745: Comparing package versions in puppet behaves differently ... Needs More Information
Related to Puppet - Bug #20221: Cannot install the latest release of a specific package v... Needs More Information


#1 Updated by Anonymous about 4 years ago

  • Status changed from Unreviewed to Accepted

#2 Updated by Zachary Stern over 2 years ago

  • Keywords set to customer

Also available in: Atom PDF