Description of problem: Multiple image streams that support jee when creating new application. Version-Release number of selected component (if applicable): 3.1 How reproducible: 100% Steps to Reproduce: 1. Upgraded from 3.0 to 3.1 2. Ran # oc replace -n openshift -f /usr/share/openshift/examples/xpaas-streams imagestream "jboss-webserver3-tomcat7-openshift" replaced imagestream "jboss-webserver3-tomcat8-openshift" replaced imagestream "jboss-eap6-openshift" replaced imagestream "jboss-amq-6" replaced 3. Then # oc new-app https://github.com/42sixsolutions/claire.git -n test error: multiple images or templates matched "jee": 2 Actual results: error: multiple images or templates matched "jee": 2 Expected results: Choose the correct is to use and not error trying to use multiple. Additional info: # oc get imagestream -n openshift -o yaml | grep jee -B6 -A3 spec: dockerImageRepository: registry.access.redhat.com/jboss-amq-6/amq-openshift tags: - annotations: description: JBoss ActiveMQ 6 broker image. iconClass: icon-jboss supports: amq:6.2,jee,java tags: javaee version: "6.2" name: "6.2" -- spec: dockerImageRepository: registry.access.redhat.com/jboss-eap-6/eap-openshift tags: - annotations: description: JBoss EAP 6 STI images. iconClass: icon-jboss supports: eap:6.4,jee,java tags: javaee version: "6.4" name: "6.4"
This is working as designed, the repository is identified as containing a java application, and there are two imagestreamtags which "support" java, there's no way to choose between them. the only change that could be considered here is to remove "java" from the "supports" list on the AMQ image. Assigning to the middleware team to update that.
Rob/Kevin, the "supports" annotation is intended to indicate what types of applications the image can build, so it is probably not appropriate for amq since it's not a builder image.
This issue is now out of date, it is no longer a bug. Closing as "notabug" since there is no "out of date" option.