Bug 1109347 - Node.js 0.10 is reporting itself as 0.6.20
Summary: Node.js 0.10 is reporting itself as 0.6.20
Keywords:
Status: CLOSED DUPLICATE of bug 1108951
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: All
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-13 17:51 UTC by rleaf
Modified: 2015-05-15 00:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 17:55:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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