Bug #1656

Puppet rpm/yum handler cannot deal with 2 packages with the same name and a different version

Added by Robert Lazzurs over 3 years ago. Updated over 1 year ago.

Status:Duplicate Start date:10/17/2008
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:package
Target version:-
Affected Puppet version:0.24.4 Branch:
Keywords:
Votes: 2

Description

Hello,

I have hit an issue where puppet cannot manage the the facilities provided to it by rpm/yum. I tried to use puppet to ensure an extra kernel package would be installed on a system by adding the following line

package { kernel-xen: ensure => “2.6.18-92.1.6.el5” }

However when running the manifest on the server I get the following message

err: //Node[vfuk3]/productionsys/production/Package[kernel-xen]/ensure: change from 2.6.18-53.el5 to 2.6.18-92.1.6.el5 failed: Could not update: Failed to update to version 2.6.18-92.1.6.el5, got version 2.6.18-53.el5 instead at /var/lib/puppet/modules/production/manifests/init.pp:17

then after the initial puppet run the follow is reported by rpmquery

[root@vfuk3 ~]# rpmquery kernel-xen kernel-xen-2.6.18-53.el5 kernel-xen-2.6.18-92.1.6.el5

So clearly puppet has managed to install the package however due to the first time also finding another kernel-xen package installed it took the version of the first package it found and assumed the new version it had requested was not installed.

RPM does support installing two packages with the same name and different version for good reasons, if puppet is to manage rpm based systems it should too.

History

Updated by James Turnbull over 3 years ago

  • Status changed from Unreviewed to Needs More Information

Not sure I understand the problem. What’s on line 17 of the manifest? Can you provide the full manifest, traces, and debug logs please.

Updated by Trevor Hemsley over 3 years ago

This looks like the same issue that I reported in ticket #1720.

Updated by Robert Lazzurs over 2 years ago

  • Status changed from Needs More Information to Duplicate

Hello,

On line 17 of the manifest is the package line in the first report. I agree that this bug is a duplicate of the other bug linked to it. The basic issue being the puppet yum handler not handling duplicates of the same package very well.

Updated by David Miller almost 2 years ago

  • Status changed from Duplicate to Re-opened

These bugs can’t be duplicates of each other. One of them has to stay open. :) (or get closed for some other reason other than duplicate). I’m surprised the tracker actually let you do that.

Updated by James Turnbull over 1 year ago

  • Status changed from Re-opened to Duplicate

Also available in: Atom PDF