Bug 1358898

Summary: Failed to create dc using xpaas template apps
Product: OpenShift Container Platform Reporter: Vikas Laad <vlaad>
Component: TemplatesAssignee: Ben Parees <bparees>
Status: CLOSED DUPLICATE QA Contact: XiuJuan Wang <xiuwang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-21 17:53:57 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:

Description Vikas Laad 2016-07-21 17:47:45 UTC
Description of problem:
When trying to deploy eap app on Openshift 3.3 using xpaas-templates DeploymentConfig fails to create because of following error. Template needs to be updated.

    error: DeploymentConfig "eap-app" is invalid: spec.triggers[0].imageChangeParams.from.name: Invalid value: "eap-app": must be in the form of <name>:<tag>

Version-Release number of selected component (if applicable):
openshift v3.3.0.8
kubernetes v1.3.0+57fb9ac
etcd 2.3.0+git

How reproducible:
Always on Openshift 3.3

Steps to Reproduce:
1. Create an env with openshift v3.3
2. Create a new app using eap64-mysql-s2i
3. see the error 

Actual results:
    error: DeploymentConfig "eap-app" is invalid: spec.triggers[0].imageChangeParams.from.name: Invalid value: "eap-app": must be in the form of <name>:<tag>


Expected results:
DeploymentConfig should be created and app should be created.

Additional info:

Comment 1 Ben Parees 2016-07-21 17:53:57 UTC

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