Description of problem: When creating an app using the template jws31-tomcat7-https-s2i, pods fail to start. The event log shows the following error: 10m 10m 1 jws-app.153953c30c204834 BuildConfig Warning BuildConfigTriggerFailed buildconfig-controller error triggering Build for BuildConfig dakinitest-jws31-tomcat7-https-s2i-20180618/jws-app: Internal error occurred : build config dakinitest-jws31-tomcat7-https-s2i-20180618/jws-app has already instantiated a build for imageid registry.access.redhat.com/jboss-webserver-3/webserver31-tomcat7-openshift@sha256:00d6d2d4a1fd2d9a7211d83ca0401cf32ca7ed07534def8e6e9a102854e1295c Version-Release number of selected component (if applicable): oc v3.10.0-0.66.0 and oc v3.9.14 How reproducible: Always Steps to Reproduce: 1. oc new-app jws31-tomcat7-https-s2i 2. oc get events 3. oc get pods Actual results: [root@free-int-master-3c664 ~]# oc get events -n dakinitest-jws31-tomcat7-https-s2i-20180618 LAST SEEN FIRST SEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE <snip> 15m 15m 1 jws-app.153953c30c204834 BuildConfig Warning BuildConfigTriggerFailed buildconfig-controller error triggering Build for BuildConfig dakinitest-jws31-tomcat7-https-s2i-20180618/jws-app: Internal error occurred: build config dakinitest-jws31-tomcat7-https-s2i-20180618/jws-app has already instantiated a build for imageid registry.access.redhat.com/jboss-webserver-3/webserver31-tomcat7-openshift@sha256:00d6d2d4a1fd2d9a7211d83ca0401cf32ca7ed07534def8e6e9a102854e1295c [root@free-int-master-3c664 ~]# oc get pods -n dakinitest-jws31-tomcat7-https-s2i-20180618 NAME READY STATUS RESTARTS AGE jws-app-1-build 0/1 Completed 0 16m jws-app-1-deploy 0/1 Error 0 15m Expected results: Pod should enter 'Running' state. Additional info:
The above mentioned commands work for me on online-int. One important thing is that the template requires "jws-app-secret". It can be created with: oc create -f https://raw.githubusercontent.com/jboss-openshift/application-templates/master/secrets/jws-app-secret.json