Bug 1433373

Summary: Instructions for adding Fuse Integration Services templates do not work
Product: Container Development Kit (CDK) Reporter: Jeremy Davis <jeremy.davis>
Component: documentationAssignee: Nobody <nobody>
Status: MODIFIED --- QA Contact: Ondřej Pták <optak>
Severity: low Docs Contact:
Priority: unspecified    
Version: ---CC: jgreguske, kanderso, lmohanty, timoran
Target Milestone: ---   
Target Release: 2.3   
Hardware: All   
OS: Mac OS   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Attachments:
Description Flags
Fuse templates do not display after adding with oc tool
none
Fuse templates display after a search
none
Fuse templates do not display from search after choosing "Java"
none
Image is unavailable after creation none

Description Jeremy Davis 2017-03-17 13:33:23 UTC
Description of problem:

Following the instructions here: https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_for_openshift/3/html-single/red_hat_jboss_fuse_integration_services_2.0_for_openshift/

Does not result in successful creation of s2i images.  There are 2 problems:
1. The added templates do not display under "Java," and only display after a search
2. The template is not actually available after creation

Version-Release number of selected component (if applicable):
Minishift version: 1.0.0-beta.4-1
CDK Version: 3.0.0-beta.1

How reproducible:
100%


Steps to Reproduce:
1. Download CDK 3 Beta
2. Follow instructions from FIS 2.0 on installing templates

Actual results:
Templates only diplay after a search
Templates are not available for the build

Expected results:
Templates diplay as described in the documentation
The build works correctly


Additional info:

Comment 1 Jeremy Davis 2017-03-17 13:34:33 UTC
Created attachment 1264036 [details]
Fuse templates do not display after adding with oc tool

Comment 2 Jeremy Davis 2017-03-17 13:35:15 UTC
Created attachment 1264037 [details]
Fuse templates display after a search

Comment 3 Jeremy Davis 2017-03-17 13:36:05 UTC
Created attachment 1264038 [details]
Fuse templates do not display from search after choosing "Java"

Comment 4 Jeremy Davis 2017-03-17 13:37:00 UTC
Created attachment 1264039 [details]
Image is unavailable after creation

Comment 5 Jeremy Davis 2017-03-17 13:58:21 UTC
I reproduced this using CDK 2.4 as well.  The behaviour is the same.

The commands ran successfully:
"MacBook:cdk24 mac$ BASEURL=https://raw.githubusercontent.com/jboss-fuse/application-templates/GA
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/fis-image-streams.json
imagestream "fis-java-openshift" replaced
imagestream "fis-karaf-openshift" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/karaf2-camel-amq-template.json
template "s2i-karaf2-camel-amq" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/karaf2-camel-log-template.json
template "s2i-karaf2-camel-log" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/karaf2-camel-rest-sql-template.json
template "s2i-karaf2-camel-rest-sql" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/karaf2-cxf-rest-template.json
template "s2i-karaf2-cxf-rest" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-template.json
template "s2i-spring-boot-camel" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-amq-template.json
template "s2i-spring-boot-camel-amq" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-config-template.json
template "s2i-spring-boot-camel-config" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-drools-template.json
template "s2i-spring-boot-camel-drools" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-infinispan-template.json
template "s2i-spring-boot-camel-infinispan" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-rest-sql-template.json
template "s2i-spring-boot-camel-rest-sql" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-teiid-template.json
template "s2i-spring-boot-camel-teiid" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-camel-xml-template.json
template "s2i-spring-boot-camel-xml" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-cxf-jaxrs-template.json
template "s2i-spring-boot-cxf-jaxrs" replaced
MacBook:cdk24 mac$ oc replace --force -n openshift -f ${BASEURL}/quickstarts/spring-boot-cxf-jaxws-template.json
template "s2i-spring-boot-cxf-jaxws" replaced
MacBook:cdk24 mac$"

Comment 6 Robert Krátký 2017-03-17 15:11:07 UTC
Hi Jeremy,

Thanks for reporting that. It seems there are three problems:

a) The OpenShift docs don't mention that the CDK-bundled version of OpenShift doesn't include all templates.

b) CDK has an implementation problem that prevents templates from showing up.

c) CDK docs should provide a better explanation of the templates issue.

Ad a), I'm going to talk to OpenShift docs people, so that we better coordinate OpenShift and CDK docs to align the info.

Ad b), I filed https://issues.jboss.org/browse/CDK-98 for the CDK development team.

Ad c), the CDK docs team will work to improve the note in the CDK 2.4 docs (https://issues.jboss.org/browse/RHDEVDOCS-395) (no 3.0 docs available yet): https://access.redhat.com/documentation/en-us/red_hat_container_development_kit/2.4/html/getting_started_guide/using_openshift_container_platform#working_with_openshift_templates
If you have a suggestion in that regard, please, add a comment to that issue.

As both the CDK eng. and docs teams use JIRA to track issues, I propose we close this bug and continue the work in JIRA.