Bug #4335
closedImpossible to upgrade rpm packages via RPM Technique
Description
I want to upgrade rudder-agent 2.8.1 to 2.9.1. The repo file is updated and the 2.9.1 package is available.
[root@node ~]# yum list installed rudder-agent Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile Installed Packages rudder-agent.x86_64 1398866025:2.8.1.release-1.EL.5 installed
[root@node ~]# yum list available rudder-agent Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile Available Packages rudder-agent.i386 1398866025:2.9.1.release-1.EL.5 winz-rudder rudder-agent.x86_64 1398866025:2.9.1.release-1.EL.5 winz-rudder
If I tell the "Package management for RHEL / CentOS / SuSE / RPM systems" technique to upgrade it, it doesn't work.
[root@winz002512 ~]# /var/rudder/cfengine-community/bin/cf-agent -KI |grep rudder-agent 2014-01-07T14:57:36+0100 info: Q:yum --quiet check-up ...:rudder-agent.x86_64 1398866025:2.9.1.release-1.EL.5 winz-rudder 2014-01-07T14:57:41+0100 notice: R: @@packageInstallation@@result_success@@bf2236d7-9ca3-4487-a2e9-5637c680f8b1@@c924c104-9eeb-4496-871f-e9b381d41b67@@108@@RHEL/CentOS/SuSE packages@@rudder-agent@@2014-01-07 14:57:33+01:00##b32b8ca6-5c75-466b-85f2-3eb6e9ff0494@#No action required for RPM package rudder-agent with policy: update 2014-01-07T14:57:50+0100 info: Q:yum --quiet check-up ...:rudder-agent.x86_64 1398866025:2.9.1.release-1.EL.5 winz-rudder
But the old version is still there.
[root@node ~]# yum list installed rudder-agent Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile Installed Packages rudder-agent.x86_64 1398866025:2.8.1.release-1.EL.5 installed
Updated by Vincent MEMBRÉ almost 11 years ago
- Subject changed from Impossible to upgrade rpm packages to Impossible to upgrade rpm packages via RPM Technique
- Assignee set to Nicolas CHARLES
- Target version set to 2.8.2
Hmm... Seems a like a bug in detection of update needed from CFEngine.
Can a CFEngine guru come and look at that ??
It was detected in 2.8, but i suspect this happens in 2.6 too.
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.8.2 to 2.8.3
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.8.3 to 2.8.4
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.8.4 to 133
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 133 to 2.9.5
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.9.5 to 2.9.6
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.9.6 to 2.9.7
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.9.7 to 150
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 150 to 2.10.4
Updated by Nicolas PERRON over 10 years ago
- Target version changed from 2.10.4 to 2.10.5
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.10.5 to 2.10.6
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 2.10.6 to 2.10.7
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.10.7 to 2.10.8
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.10.8 to 2.10.9
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.9 to 2.10.10
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.10 to 2.10.11
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.11 to 2.10.12
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.12 to 2.10.13
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.13 to 2.10.14
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.14 to 2.10.15
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.15 to 2.10.16
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.16 to 2.10.17
Updated by Nicolas CHARLES over 9 years ago
- Related to Bug #6587: cfengine context is not updated properly when doing multiple indivudual package actions added
Updated by Nicolas CHARLES over 9 years ago
- Related to Bug #5386: rudder-agent 2.11.{0,1} ignore duplicate lines in data files causing rpmPackageInstallation technique to ignore some configurations added
Updated by Nicolas CHARLES over 9 years ago
- Related to Bug #5609: It's not possible to update package to latest version added
Updated by Nicolas CHARLES over 9 years ago
- Status changed from New to Discussion
- Assignee changed from Nicolas CHARLES to Dennis Cabooter
Dennis,
I guess that with all the other fixes we made, this ticket isn't relevant any more. Could you confirm ?
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.17 to 2.10.18
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.18 to 2.10.19
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.19 to 2.10.20
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.20 to 2.11.18
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.11.18 to 2.11.19
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.11.19 to 2.11.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by François ARMAND about 8 years ago
- Status changed from Discussion to Rejected
This is a never ending world of pain which ended with the addition of the new package techniques. So the correct, definitive solution against that is to use the new package techniques: http://www.normation.com/en/blog/2016/10/17/discover-new-package-management-implementation-rudder/