Project

General

Profile

Actions

Bug #7116

closed

Issue updating RPM using "Package management for RHEL / CentOS / SuSE / RPM systems"

Added by Kiran V over 8 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
1
Assignee:
-
Category:
-
Target version:
-
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Following are the details
Technique = "Package management for RHEL / CentOS / SuSE / RPM systems"
Technique Version = 7.0
Rudder Server Version = rudder-server-root-3.1.0.release-1.EL.6.noarch
Rudder Agent Version = rudder-agent-3.1.0.release-1.EL.5

Issue description : Trying to upgrade zabbix-2.0.4-1.el5 to zabbix-2.4.5-1.el5. the same works flawlessly using yum, the compliance report show 100%, however change is not seen on destination node.

For Directive config ,refer attached png.

Refer log for more info.Command used to generate log => /var/rudder/cfengine-community/bin/cf-agent -Klvb check_rpm_package_installation


Files

rpm-update-directive.png (28.5 KB) rpm-update-directive.png Kiran V, 2015-08-19 10:06
rudder-rpm.log (1.18 MB) rudder-rpm.log Kiran V, 2015-08-19 10:07
rpm-update.png (26.7 KB) rpm-update.png Kiran V, 2015-08-26 11:48

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #7119: Wrong reporting in rpmPackageInstallation when trying to update a non-existent packageRejectedActions
Actions #1

Updated by Alexis Mousset over 8 years ago

The package name should be "zabbix", and the version "2.0.4-1.el5" (if you want to specify it, but in the screenshot the selected version is the package manager default version).

It should have been reported as an error, and I opened another issue for this (#7119).

Actions #2

Updated by Alexis Mousset over 8 years ago

  • Related to Bug #7119: Wrong reporting in rpmPackageInstallation when trying to update a non-existent package added
Actions #3

Updated by Kiran V over 8 years ago

Thank you Alexis for the information.

the attached conf worked.

the issue was also with gpgcheck. disabled gpgcheck and the directive worked, it would be great if directive also provides option to override directive.

Actions #4

Updated by Kiran V over 8 years ago

Kiran V wrote:

Thank you Alexis for the information.

the attached conf worked.

the issue was also with gpgcheck. disabled gpgcheck and the directive worked, it would be great if directive also provides option to override gpgcheck.

Actions #5

Updated by Alexis Mousset about 8 years ago

  • Status changed from New to Rejected

Resolved issue.

Actions

Also available in: Atom PDF