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

Bug 1201399

Summary: Fail to install nodejs cartridge with rhscl-2.0 - OSE 2.1
Product: OpenShift Container Platform Reporter: John W. Lamb <jolamb>
Component: InstallerAssignee: John W. Lamb <jolamb>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 2.1.0CC: bleanhar, jialiu, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, pruan, tdawson, xiama
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nodejs010-nodejs-express-3.2.5-3.el6op Doc Type: Bug Fix
Doc Text:
Cause: Package dependency version specifier for nodejs "mkdirp" package was too specific. Consequence: The package "nodejs010-nodejs-express" wouldn't install on systems where nodejs "mkdirp" package would satisfy dependency, but which had a more recent version than what was specified in the package dependencies. This prevented the nodejs cartridge dependencies from being satisfied, thus preventing the nodejs cartridge from installing. Fix: Change nodejs "mkdirp" dependency version specifier to (correctly) include versions greater than or equal to 0.3.4. Result: "nodejs010-nodejs-express" package no longer fails to install, and the nodejs cartridge now installs properly.
Story Points: ---
Clone Of: 1198409 Environment:
Last Closed: 2015-08-11 17:37:33 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: 1198409, 1201400    
Bug Blocks: 1241887    

Comment 3 Ma xiaoqiang 2015-03-13 07:10:36 UTC
Install nodejs cartridge successfully for ose-2.1 with rhscl-2.0

Comment 4 John W. Lamb 2015-07-13 20:44:11 UTC
*** Bug 1241878 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2015-08-11 17:37:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1589.html