Bug #2384
closed
Modifying /var/rudder/configuration-repository/policy-templates/systemSettings/misc/clockConfiguration/1.0/clockConfiguration.st to have the package method for redhat to use yum_rpm instead of yum appears to fix the issue.
- Status changed from New to Discussion
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
Adjusting the package method just this time does not look like the right way to do it to me... I think we should use our copy of it (without the bulk installation method that breaks reports) and propagate this to all the techniques that use yum !
- Target version changed from 2.3.7 to 2.3.8
- Project changed from Rudder to 24
- Category deleted (
Techniques)
- Category set to Policy Templates
It concerns Policy Templates
- Target version changed from 2.3.8 to 2.3.9
- Status changed from Discussion to In progress
Picking this up after several months of silence - this appears to have slipped through our net, sorry about that.
The difference between package_methods "yum" and "yum_rpm" that causes this to work is the package_name_convention => "$(name)" (instead of "$(name).$(arch)". This is also correct in the package_method "generic", which we also use in almost all other Techniques. Let's just use this one.
I will also open another ticket to ensure that we have a standard approach to using only package_method generic, unless we have a good reason to, to avoid any other bugs of this type.
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:b4ca82600f129ada7af5c3e91ceb39d7aa3a1c09.
Jonathan CLARKE wrote:
I will also open another ticket to ensure that we have a standard approach to using only package_method generic, unless we have a good reason to, to avoid any other bugs of this type.
That's #2977.
- Status changed from Pending technical review to Released
- Project changed from 24 to Rudder
- Category changed from Policy Templates to Techniques
Also available in: Atom
PDF