Bug 1278577 - JBoss Fuse 6.1 cartridge is out of date
Summary: JBoss Fuse 6.1 cartridge is out of date
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Rory Thrasher
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 20:24 UTC by sjavurek
Modified: 2015-12-21 16:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-21 16:09:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description sjavurek 2015-11-05 20:24:31 UTC
Description of problem:

The existing Fuse Cartridge in OSO 2.X is out of date and does not work well. We have a customer who was trying out the cartridge using the camel-cxf component. This feature does not install properly and results in an error. 

After discussing with the Fuse Engineering team, I understand that our cartridge is much older than what is available in OSE and that we should redirect customers accordingly. 

There are two points of concern here:

1. Having a broken cartridge is much worse than not having a cartridge at all. It sets a bad impression and for some customers, they may not even contact us. 

2. This customer is reluctant to work on OSE as they have to renew their trial period every 30 days. We need to extend that period for them while we sort out the issues on OSO. 

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


How reproducible:


Steps to Reproduce:

Fuse 6.1 @ openshift
Console URL: http://fuse-cibc.rhcloud.com
Console User: admin
Console Password:   KF5P7_bFXuUG

One case the fuse container has failed with a provisioning error. Drilling into the profile, we are only trying to deploy camel-cxf.

There is no apparent workaround.

Actual results:


Expected results:


Additional info:


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