Project

General

Profile

Actions

Question #7932

closed

Multiple Package Install

Added by remus dragomir about 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
-
Regression:

Description

Hi all,

Is there any better method of installing multiple packages than just using a list of yum commands in a post-modification hook section?
The directive for installing a package is, apparently, installing one package at a time. And if I use "add another" package to the same directive, it creates a whole new section, thus making it very difficult to maintain, in my case, custom OS-based lists of packages to be installed.
Another way I've tried was having a parameter keep the list of packages to be installed, but because of the yum install technique, I had to separate the packages in the list as follows;
"meld \
talk"
And so it always reports

RPM package meld \ talk; with policy: add could not be repaired
RPM package meld \ talk; with policy: add could not be repaired,

even when it installs both packages in the list. It reports no error if I use them as a <space> separated list: "meld talk". but the lists are often quite extensive.
Please advise.

Thanks.
Remus

Actions #1

Updated by Alexis Mousset over 7 years ago

  • Category set to Generic methods
Actions #2

Updated by Benoît PECCATTE over 7 years ago

  • Project changed from 41 to Rudder
  • Category changed from Generic methods to Web - Config management
  • Status changed from New to Discussion

The problem is that we cannot have proper reporting if we install multiple packages at once.
There is no way to do it simply in the base rudder techniques, but you can create a new technique using the technique editor:
- Use variable_iterator to create and iterator based on your package list (you can put the full list in a single parameter)
- Then user package install that will automatically iterate on the list

Actions #3

Updated by remus dragomir over 7 years ago

I'll try it.
You can close this ticket. Thank you.

Remus

Actions #4

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from Discussion to Resolved

OK, closing.

Actions

Also available in: Atom PDF