Project

General

Profile

Bug #5496

RPM package always repaired, but not installed

Added by Dennis Cabooter about 4 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
1
Assignee:
-
Category:
Techniques
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Pull Request:
Priority:
0

Description

  • Technique name: Package management for RHEL / CentOS / SuSE / RPM systems
  • Technique version: 5.1
  • Package to be installed: gd.i386

This is what is installed:

# yum list installed gd | tail -1
gd.x86_64                      2.0.33-9.4.el5_4.2                      installed

This is what i found in the logs:

2014-09-08T11:07:16+0200  verbose: /default/check_rpm_package_installation/packages/'gd.i386'[0]: Running /usr/bin/yum -y install gd.i386-* in shell
2014-09-08T11:07:16+0200  verbose: /default/check_rpm_package_installation/packages/'gd.i386'[0]: Executing /usr/bin/yum -y install gd.i386-*...
2014-09-08T11:07:17+0200     info: /default/check_rpm_package_installation/packages/'gd.i386'[0]: Q:yum -y install gd.i3 ...:Loaded plugins: fastestmirror, priorities, security
2014-09-08T11:07:17+0200     info: /default/check_rpm_package_installation/packages/'gd.i386'[0]: Q:yum -y install gd.i3 ...:Loading mirror speeds from cached hostfile
2014-09-08T11:07:17+0200     info: /default/check_rpm_package_installation/packages/'gd.i386'[0]: Q:yum -y install gd.i3 ...:Setting up Install Process
2014-09-08T11:07:17+0200     info: /default/check_rpm_package_installation/packages/'gd.i386'[0]: Q:yum -y install gd.i3 ...:No package gd.i386-* available.
2014-09-08T11:07:17+0200     info: /default/check_rpm_package_installation/packages/'gd.i386'[0]: Q:yum -y install gd.i3 ...:Nothing to do

Which is correct:

# yum install gd.i386-*
Loaded plugins: fastestmirror, priorities, security
Loading mirror speeds from cached hostfile
Setting up Install Process
No package gd.i386-* available.
Nothing to do

It should be installed like this (mind the omitted dash):

# yum install gd.i386*
Loaded plugins: fastestmirror, priorities, security
Loading mirror speeds from cached hostfile
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package gd.i386 0:2.0.33-9.4.el5_4.2 set to be updated
--> Finished Dependency Resolution

In the past the technique did install the correct package - i386 on a 64 bit system. Can't remember the last version of Rudder/technique where it was still working.


Related issues

Has duplicate Rudder - Bug #5850: rpmPackageInstallation v6.1 allways re-install packageRejected2014-11-27

History

#1 Updated by Matthieu CERDA about 4 years ago

  • Status changed from New to Discussion
  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE

Hm, this is indeed a problem, maybe linked to the port to ncf and the usage of the stock stdlib again. Benoît, do you know if something has been changed recently in this Technique ?

#2 Updated by Benoît PECCATTE about 4 years ago

  • Assignee changed from Benoît PECCATTE to Matthieu CERDA

Sorry I don't know

#3 Updated by Matthieu CERDA about 4 years ago

  • Target version changed from 2.11.3 to 2.11.4

#4 Updated by Matthieu CERDA almost 4 years ago

I tested this, it seems that CFEngine now really expects us to specify package_architecture => { "arch" }; to make this work...

#5 Updated by Dennis Cabooter almost 4 years ago

That sounds better to me than to specify it in the package name. Does it mean that the tecnique needs an additional checkbox to choose between i386 and x86_64?

#6 Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.11.4 to 2.11.5

#7 Updated by Dennis Cabooter almost 4 years ago

This is still not fixed. At the moment I can't reliably install (i386) packages on RHEL/CentOS.

#8 Updated by Dennis Cabooter almost 4 years ago

  • Priority changed from 3 to 1

Also reporting is flaky:

fuse            Error taking action for RPM package fuse with policy: add                          Error
fuse-ntfs-3g    Performed repair action for RPM package fuse-ntfs-3g to comply with policy: add    Repaired
gd.i386         Performed repair action for RPM package gd.i386 to comply with policy: add         Repaired

And now the real situation for these packages:

# rpm -qa --qf "%{n}-%{arch}\n" fuse
fuse-x86_64
# rpm -qa --qf "%{n}-%{arch}\n" fuse-ntfs-3g
fuse-ntfs-3g-x86_64
# rpm -qa --qf "%{n}-%{arch}\n" gd
gd-x86_64
gd-i386

In other words Rudder reporting on this is really wrong; I can't rely on it.

#9 Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.11.5 to 2.11.6

#10 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.6 to 2.11.7

#11 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.7 to 2.11.8

#12 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.8 to 2.11.9

#13 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.9 to 2.11.10

#14 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.10 to 2.11.11

#15 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.11 to 2.11.12

#16 Updated by Dennis Cabooter over 3 years ago

Please can someone look at this again? Nothing happened untill now.

#17 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.12 to 2.11.13

#18 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.13 to 2.11.14

#19 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.14 to 2.11.15

#20 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.15 to 2.11.16

#21 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.16 to 2.11.17

#22 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.17 to 2.11.18

#23 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.18 to 2.11.19

#24 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.19 to 2.11.20

#25 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.20 to 2.11.21

#26 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.21 to 2.11.22

#27 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.22 to 2.11.23

#28 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#29 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.24 to 308

#30 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 308 to 3.1.14

#31 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.14 to 3.1.15

#32 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.15 to 3.1.16

#33 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.16 to 3.1.17

#34 Updated by Benoît PECCATTE almost 2 years ago

  • Assignee deleted (Matthieu CERDA)

#35 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.17 to 3.1.18

#36 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.18 to 3.1.19

#37 Updated by François ARMAND over 1 year ago

  • Status changed from Discussion to Rejected
  • Priority set to 0

I'm closing that ticket because we created new package technique for exactly that kind of problem. Please feel free to reopen the ticket if the problem persists with them.

Also available in: Atom PDF