Bug #11995

Add group install to Package

Added by Charlie Wyse 4 months ago. Updated 4 months ago.

Status:Duplicate Start date:01/17/2012
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:package
Target version:-
Affected Puppet version:2.6.12 Branch:
Keywords:yum redhat
Votes: 0

Description

This is my first ticket so if I do anything wrong let me know. When trying to install a package group in Red Hat 6, I get a failure. I don’t think puppet understands package groups. Could this be added to the package feature?

My manifest: package { ‘MRG Grid’:

            ensure  => present,
    }

Error: err: /Stage[main]/Mrg/Package[MRG Grid]/ensure: change from absent to present failed: Execution of ‘/usr/bin/yum -d 0 -e 0 -y install MRG Grid’ returned 1: Error: Nothing to do

If the package could have a command to encapsulate anything in the naming list like ‘MRG Grid’ and change install to groupinstall, this should do the trick.

Example: ‘/usr/bin/yum -d 0 -e 0 -y groupinstall “MRG Grid”’

Anyhow, as I said this is my first ticket so let me know what I can do to help move this along without any helpful knowledge in ruby programming.

Related issues

duplicates Puppet - Bug #5175: yum provider + package groups giving unnecessary errors Accepted 11/02/2010

History

#1
Updated by Peter Meier 4 months ago

Imho this was already discussed a couple of times (mailing list, probably also bugtracker). One (big) issue is that you can tell yum to install a group, but afair you can’t query yum if a certain group is installed. So how would you do that, to fit into puppet’s idea of managing state of resources?

#2
Updated by Charlie Wyse 4 months ago

That is a very good point and explains why it wasn’t in there yet. Some code around doing a “yum groupinfo <%= GROUP NAME %>” then searching for any packages listed under “Mandatory Packages”. Finally using the regular rpm check on each package listed would be necessary. So it is possible for a more advanced ruby programmer than I. Currently I’m just using an exec string to get the job done, or I guess since ‘MRG Grid’ only needs 3 packages I could make there separate package lines. But this feature would be very helpful to many admins that would like to have a desktop class that installs ‘GNOME Desktop’ or in my case a server group that needs MRG.

#3
Updated by Dominic Cleal 4 months ago

  • Category set to package
  • Status changed from Unreviewed to Duplicate
  • Affected Puppet version set to 2.6.12
  • Keywords set to yum redhat
  • Branch deleted (puppet-2.6.12-1)

The state problem is a big issue, particularly if the contents of the groups change in comps.xml. We’ve already got #5175 open and accepted so I’m going to close this as a dupe and discussion can be continued there.

Thanks for the submission!

Also available in: Atom PDF