Modify

Ticket #1114 (accepted defect)

Opened 7 years ago

Last modified 6 years ago

bcfg2 client does not install YUMng packages if they are provided by other packages

Reported by: https://www.google.com/accounts/o8/id?id=AItOawn0s7RDAZJqmy8qhaS8PFtgoke6VxxZKSI Owned by: https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc
Priority: major Milestone: Bcfg2 1.3.5 Release (Bugfix)
Component: bcfg2-client Version: 1.0
Keywords: yum, rpm Cc: jsbillin@…

Description

We provide LPRng packages for our RHEL6 workstations, which also have cups installed due to dependencies. The LPRng and cups packages we build are:

# yum list LPRng cups
Installed Packages
cups.x86_64                      1:1.4.2-44.el6_2.3                     @updates
Available Packages
LPRng.x86_64                       3.8.28-3.caen.el5                       bcfg2

When bcfg2 runs, it fails to install LPRng even though we specify it as a package to install in the configuration. Here is what we see in the debug log:

Verifying package instances for LPRng
LPRng appears to be provided by:
  1:cups-1.4.2-44.el6_2.3.x86_64
Verifying: LPRng-None-3.caen.el5
  Not checking version for virtual package

and the LPRng package is not installed. Now, if I ask yum to install it on the command line, it doesn't have a problem:

# yum install LPRng
Loaded plugins: refresh-packagekit, security
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package LPRng.x86_64 0:3.8.28-3.caen.el5 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package        Arch            Version                    Repository      Size
================================================================================
Installing:
 LPRng          x86_64          3.8.28-3.caen.el5          bcfg2          640 k

Transaction Summary
================================================================================
Install       1 Package(s)

Total download size: 640 k
Installed size: 1.5 M
Is this ok [y/N]: y
Downloading Packages:
LPRng-3.8.28-3.caen.el5.x86_64.rpm                       | 640 kB     00:00     
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : LPRng-3.8.28-3.caen.el5.x86_64                               1/1 

Installed:
  LPRng.x86_64 0:3.8.28-3.caen.el5                                              

Complete!

Now, in the debug log, I see:

Verifying package instances for LPRng
Verifying: LPRng-None-3.caen.el5

I find the "None" part rather odd here, but I haven't figured out why it's failing.

What I do suspect is that the VerifyPackage? function in the YUMng.py Tool just automatically verifies the LPRng package no matter what, because it determines that it is a Virtual Package. Cups gets installed as normal, and the cups package claims to provide LPRng:

# rpm -q --provides cups|grep LPRng
LPRng = 3.8.15-4

Now, LPRng 3.8.28-3 is newer than 3.8.15-4, so it really should be allowing LPRng to be installed. Bcfg2 seems to see any package that claims to provide the package name to pass through VerifyPackage? as verified, and does NOT perform any kind of version checking.

Also, seeing the "None" in the version in the debugging log makes me wonder if something about the package object in the YUMng plugin is getting things confused.

Attachments

Change History

comment:1 Changed 7 years ago by https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc

  • Owner changed from desai to https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc
  • Status changed from new to accepted

comment:2 Changed 7 years ago by solj

  • Milestone changed from Bcfg2 1.2.3 Release (Bugfix) to Bcfg2 1.3.0 Release

Moving to 1.3

comment:3 Changed 6 years ago by solj

  • Milestone changed from Bcfg2 1.3.0 Release to Bcfg2 1.3.2 Release (Bugfix)

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as accepted
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.