Bug 1241878 - OSE-2.1: Can not update system due to nodejs010-nodejs-express dependency.
Summary: OSE-2.1: Can not update system due to nodejs010-nodejs-express dependency.
Keywords:
Status: CLOSED DUPLICATE of bug 1201399
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: John W. Lamb
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks: 1241887
TreeView+ depends on / blocked
 
Reported: 2015-07-10 10:02 UTC by Johnny Liu
Modified: 2015-07-13 20:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1241887 (view as bug list)
Environment:
Last Closed: 2015-07-13 20:44:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Johnny Liu 2015-07-10 10:02:15 UTC
Description of problem:
On an existing ose-2.1.z node system, run "yum update", get the following error:
# yum update
<--snip-->
--> Processing Dependency: nodejs010-npm(mkdirp) < 0.4 for package: nodejs010-nodejs-express-3.2.5-2.el6op.noarch
--> Finished Dependency Resolution
Error: Package: nodejs010-nodejs-express-3.2.5-2.el6op.noarch (@openshift_node_cdn)
           Requires: nodejs010-npm(mkdirp) < 0.4
           Removing: nodejs010-nodejs-mkdirp-0.3.5-3.el6.noarch (@rhscl)
               nodejs010-npm(mkdirp) = 0.3.5
           Updated By: nodejs010-nodejs-mkdirp-0.5.0-1.el6.noarch (rhscl)
               nodejs010-npm(mkdirp) = 0.5.0
           Available: nodejs010-nodejs-mkdirp-0.3.5-2.el6_4.noarch (rhscl)
               nodejs010-npm(mkdirp) = 0.3.5
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

# rpm -q nodejs010-nodejs-express
nodejs010-nodejs-express-3.2.5-2.el6op.noarch

# rpm -qR nodejs010-nodejs-express-3.2.5-2.el6op.noarch|grep mkdi
nodejs010-npm(mkdirp) >= 0.3.4
nodejs010-npm(mkdirp) < 0.4


# yum list --showdup nodejs010-nodejs-mkdirp
Loaded plugins: priorities, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
94 packages excluded due to repository priority protections
Installed Packages
nodejs010-nodejs-mkdirp.noarch                                                                    0.3.5-3.el6                                                                      @rhscl
Available Packages
nodejs010-nodejs-mkdirp.noarch                                                                    0.3.5-2.el6_4                                                                    rhscl 
nodejs010-nodejs-mkdirp.noarch                                                                    0.3.5-3.el6                                                                      rhscl 
nodejs010-nodejs-mkdirp.noarch                                                                    0.5.0-1.el6                                                                      rhscl 


The root cause is that rhscl released a new version of nodejs010-nodejs-mkdirp.noarch (0.5.0-1.el6), but in ose-2.1 channel, nodejs010-nodejs-express-3.2.5-2.el6op.noarch still has dependency with old version. It would cause conflicts.

In ose-2.2, it is working well, because ose-2.2 is using nodejs010-nodejs-express-3.2.5-3.el6op.noarch, it has different dependency.
# rpm -qR nodejs010-nodejs-express|grep mkdi
nodejs010-npm(mkdirp) >= 0.3.4



Version-Release number of selected component (if applicable):
2.1.z released version
nodejs010-nodejs-express-3.2.5-2.el6op.noarch

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 John W. Lamb 2015-07-13 20:44:11 UTC
This is actually a duplicate of bug 1201399, which should have been addressed with the release of 2.1.11. The 2.1.11 advisory, however was never released. This advisory will be released at the same time as 2.1.12.

*** This bug has been marked as a duplicate of bug 1201399 ***


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