Description of problem: Creating JWS MongoDB app in Openshift 3.5 is not accessible. Version-Release number of selected component (if applicable): openshift v3.5.0.5+8f2840d kubernetes v1.5.2+43a9be4 etcd 3.1.0-rc.0 How reproducible: Always Steps to Reproduce: 1. oc new-project test 2. oc create -f https://raw.githubusercontent.com/jboss-openshift/application-templates/master/secrets/jws-app-secret.json 3. oc new-app --template=openshift/jws30-tomcat7-mongodb-s2i after the build and deploy runs successfully curl on route or svc returns blank root@ip-172-31-41-173: ~/svt/openshift_scalability # oc get pods NAME READY STATUS RESTARTS AGE jws-app-1-build 0/1 Completed 0 11m jws-app-1-k6n6g 1/1 Running 0 10m jws-app-mongodb-1-mhx66 1/1 Running 0 11m root@ip-172-31-41-173: ~/svt/openshift_scalability # oc get routes NAME HOST/PORT PATH SERVICES PORT TERMINATION jws-app jws-app-vlaadjws.0118-soa.qe.rhcloud.com jws-app <all> secure-jws-app secure-jws-app-vlaadjws.0118-soa.qe.rhcloud.com secure-jws-app <all> passthrough root@ip-172-31-41-173: ~/svt/openshift_scalability # curl jws-app-vlaadjws.0118-soa.qe.rhcloud.com root@ip-172-31-41-173: ~/svt/openshift_scalability # oc get svc NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE jws-app 172.26.144.93 <none> 8080/TCP 12m jws-app-mongodb 172.26.154.233 <none> 27017/TCP 12m secure-jws-app 172.26.57.136 <none> 8443/TCP 12m root@ip-172-31-41-173: ~/svt/openshift_scalability # curl 172.26.144.93:8080 Actual results: No response from app route Expected results: No response from app route, it should return the TODO list page Additional info:
Created attachment 1242824 [details] deploy logs
Ben I'm guessing this is another duplicate of the OpenShift issue although there are no build logs to confirm.
Yeah, certainly looks like it. Any s2i build that uses a context dir would be impacted by 1414960. *** This bug has been marked as a duplicate of bug 1414960 ***