Bug 1109347

Summary: Node.js 0.10 is reporting itself as 0.6.20
Product: OpenShift Online Reporter: rleaf
Component: ImageAssignee: Ben Parees <bparees>
Status: CLOSED DUPLICATE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 2.xCC: jofernan, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 17:55:43 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:

Description rleaf 2014-06-13 17:51:22 UTC 
Description of problem:
After creating a new application on OpenShift Online and attaching a Node.js 0.10 cartridge to it, I'm having difficulty getting my application to recognize the cartridge as a Node.js 0.10 cartridge.

Running 'node -v' in an SSH session with the cartridge gives an unexpected value.

Version-Release number of selected component (if applicable):
0.10

How reproducible:
Very

Steps to Reproduce:
1. Create a new application with a Node.js v0.10 cartridge.
2. SSH into the application.
3. Run 'node -v'.

Actual results:
v0.6.20

Expected results:
v0.10

Additional info:
None
Comment 1 rleaf 2014-06-13 17:55:43 UTC 

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