Bug 1008262 - package "libcgroup-pam-0.37-7.2.el6_4.x86_64" can not be installed on RHEL6.5
Summary: package "libcgroup-pam-0.37-7.2.el6_4.x86_64" can not be installed on RHEL6.5
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 1.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Brenton Leanhardt
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-16 02:48 UTC by Ma xiaoqiang
Modified: 2016-07-04 00:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-04 14:34:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ma xiaoqiang 2013-09-16 02:48:06 UTC
Description of problem:
Many openshift packages have dependecny with "libcgroup-pam-0.37-7.2.el6_4.x86_64" which can not be installed on RHEL6.5

Version-Release number of selected component (if applicable):
1.2/2013-09-11.1 puddle
http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL6.5-20130905.1/6.5/Server/x86_64/os/

How reproducible:
always

Steps to Reproduce:
1. Install openshift-origin-msg-node-mcollective on RHEL6.5
yum install  openshift-origin-msg-node-mcollective

Actual results:
package can not be installed 
#yum install  openshift-origin-msg-node-mcollective
libcgroup-pam-0.37-7.2.el6_4.x86_64 (openshift_node)
           Requires: libcgroup = 0.37-7.2.el6_4
           Installed: libcgroup-0.40.rc1-2.el6.x86_64 (@anaconda-RedHatEnterpriseLinux-201309051642.x86_64/6.5)
               libcgroup = 0.40.rc1-2.el6

Expected results:
package should be installed successfully

Additional info:

Comment 3 Gaoyun Pei 2013-09-26 07:21:09 UTC
Verify this bug on RHEL-6.5-Beta-1.3: http://download.lab.bos.redhat.com/rel-eng/RHEL-6.5-Beta-1.3/ with puddle 1.2/2013-09-23.2

The new puddle uses libcgroup-pam-0.40.rc1-3.el6.x86_64 now, no related dependency issue happens.


Note You need to log in before you can comment on or make changes to this bug.