Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1241887

Summary: OSE-2.0: Can not update system due to nodejs010-nodejs-express dependency.
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: ContainersAssignee: John W. Lamb <jolamb>
Status: CLOSED DUPLICATE QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: high    
Version: 2.0.0CC: anli, bleanhar, jokerman, jolamb, libra-bugs, libra-onpremise-devel, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1241878 Environment:
Last Closed: 2015-07-13 20:45:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1201399, 1241878    
Bug Blocks:    

Description Johnny Liu 2015-07-10 10:31:10 UTC
+++ This bug was initially created as a clone of Bug #1241878 +++

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:45:38 UTC
This is actually a duplicate of bug 1201400, which should have been addressed with the release of 2.0.9. The 2.0.9 advisory, however was never released. This advisory will be released at the same time as 2.0.10.

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