Bug #3619
closed
Package management for RHEL / CentOS / SUSE / RPM systems Error status
Added by Dennis Cabooter over 11 years ago.
Updated over 9 years ago.
Description
After upgrading from 2.5 to 2.6 all RPM packages report Error. nevertheless they are installed a long time ago by hand or Rudder 2.5.
R: @packageInstallation
@result_error@21c38298-7e0e-465e-9cd2-c6214197f16f
@4e065eb7-a27c-4087-8b22-1fa1136268ad@31
@RHEL/CentOS/SuSE packages@git
@2013-06-03 10:13:01+02:00##09a115e7-8322-4089-9d7d-00d647ece18f@#Error taking action for RPM package git with policy: add
R: @packageInstallation
@result_error@21c38298-7e0e-465e-9cd2-c6214197f16f
@32a09e48-4f48-4798-8582-460c8809e7d2@31
@RHEL/CentOS/SuSE packages@vim-enhanced
@2013-06-03 10:13:01+02:00##09a115e7-8322-4089-9d7d-00d647ece18f@#Error taking action for RPM package vim-enhanced with policy: add
R: @packageInstallation
@result_error@21c38298-7e0e-465e-9cd2-c6214197f16f
@4e065eb7-a27c-4087-8b22-1fa1136268ad@31
@RHEL/CentOS/SuSE packages@etckeeper
@2013-06-03 10:13:01+02:00##09a115e7-8322-4089-9d7d-00d647ece18f@#Error taking action for RPM package etckeeper with policy: add
- Status changed from New to Discussion
Which version of the Technique Package management for RHEL / CentOS / SUSE / RPM systems did you used to have these errors ? Did you change the versions of the Technique after the upgrade ?
It could be an error returned by the package manager which have been caught by CFEngine, it is easy to test:
On CentOS:
yum install git
echo $?
If the code is not 0, this is considered a an error
The problem is that the packages are already installed by Rudder 2.5. Rudder 2.5 reported Success, which is true, while Rudder 2.6 reports Error.
# yum install git
Loaded plugins: etckeeper, rhnplugin, security
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Install Process
Package git-1.7.4.1-1.el5.x86_64 already installed and latest version
Nothing to do
# echo $?
0
# rpm -qa | grep git
git-1.7.4.1-1.el5
Somehow this issue has been resolved automagically.
Dennis Cabooter wrote:
Somehow this issue has been resolved automagically.
Automagically ? didn't you updated the Technique ?
I'm not sure. I copied the techniques from /opt/rudder/share/techniques/ to /var/rudder/configuration-repository, dit a Git commit and reloaded the technique lib. It looks like this solved the problem.
Dennis Cabooter wrote:
I'm not sure. I copied the techniques from /opt/rudder/share/techniques/ to /var/rudder/configuration-repository, dit a Git commit and reloaded the technique lib. It looks like this solved the problem.
Ok, I'm pretty sure this is what happened :)
What was the version of the previous Rudder ?
The version of the current Rudder is 2.6.${latest} and the version of the previous Rudder is 2.5.${latest}.
- Target version changed from 2.6.2 to 2.6.3
- Target version changed from 2.6.3 to 2.6.4
- Assignee set to Jonathan CLARKE
We never be able to reproduce this bug, should we reject it ?
- Status changed from Discussion to Rejected
Nicolas PERRON wrote:
We never be able to reproduce this bug, should we reject it ?
It is unfortunate that we have never been able to reproduce this, or determine why it happened.
However, there have been quite a few fixes to rpmPackageInstallation recently, hopefully they correct whatever happened here... I don't like closing a bug without knowing why, but since Dennis' installation "fixed itself", and we have no way of knowing how to reproduce this, OK.
Please re-open if this occurs again.
- Project changed from 24 to Rudder
- Category set to Techniques
Also available in: Atom
PDF