On Fri, Aug 11, 2017 at 12:07 PM, Bamacharan Kundu <[email protected]> wrote:
> > > On 08/11/2017 09:22 PM, Ben Parees wrote: > > > > > > On Fri, Aug 11, 2017 at 11:09 AM, Bamacharan Kundu <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi Ben, > > > > On 08/11/2017 07:37 PM, Ben Parees wrote: > > > > > > > > > On Thu, Aug 10, 2017 at 12:48 PM, Bamacharan Kundu < > [email protected] <mailto:[email protected]> > > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > > > Hi, > > > I am having one build chain with openshift/origin:v3.6.0. > where > > > > > > 1. First build is triggered using custom build strategy > manually. pushes > > > newly created image to an imagestream. > > > 2. Second build is triggered based on image change in image > stream tag. > > > > > > Now, the first build is working normally and pushing the image > to the > > > specific image stream. But the second build is not getting > triggered. > > > > > > This works fine with v1.2.1. Also I have enabled > > > "system:build-strategy-custom", even tried adding > cluster-admin cluster > > > role to the user, but no luck. > > > > > > Any suggestion for what should I be looking at, or if I am > missing > > > something. > > > > > > pasting the build trigger template below for reference. > > > > > > > > > can you paste the output of "oc get bc test -o yaml" too? That > will > > > give us more insight about the state of your triggers. > > > > output of `oc get bc test -o yaml` > > http://pastebin.centos.org/148271/ <http://pastebin.centos.org/ > 148271/> > > > > > > > > also "oc get is ${JOBID} -o yaml" (where you replace $JOBID with > the > > > actual imagestream name) > > > > out put of `oc get is python -o yaml` is > > http://pastebin.centos.org/148246/ <http://pastebin.centos.org/ > 148246/> > > > > I am not able to find anything, any suggestion would be of great > help. > > > > > > I don't see anything obviously wrong either, which makes me suspect > > permissions issues as Clayton did. > > Yeah, but I even tried setting user as custer-admin for triggering the > builds. Setting a fresh cluster again and checking. > > > > Further investigation requires level 5 logs from your master, during the > > time period in which you created the imagestream and buildconfig. > You mean the opanshift logs at the time of builds running, or build > config creation time? > in your case, both since you're using the creation of one image to trigger the build of another. > > Thanks > Bamacharan > > > > > > > > > > > Thanks > > Bamacharan > > > > > > > > > > > > > > > > > { > > > "kind": "BuildConfig", > > > "apiVersion": "v1", > > > "metadata": { > > > "name": "test" > > > }, > > > "spec": { > > > "triggers": [ > > > { > > > "type": "Generic", > > > "generic": { > > > "secret": "${BUILD_TRIGGER_SECRET}" > > > } > > > }, > > > { > > > "type": "ImageChange", > > > "imageChange": { > > > "from": { > > > "kind": "ImageStreamTag", > > > "name": "${JOBID}:test" > > > } > > > } > > > } > > > ], > > > "strategy": { > > > "type": "Custom", > > > "customStrategy": { > > > "exposeDockerSocket": true, > > > "from": { > > > "kind": "DockerImage", > > > "name": "cccp-test" > > > } > > > > > > Thanks & Regards > > > Bamacharan Kundu > > > > > > _______________________________________________ > > > dev mailing list > > > [email protected] > > <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>> > > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > <http://lists.openshift.redhat.com/openshiftmm/listinfo/dev> > > > <http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > <http://lists.openshift.redhat.com/openshiftmm/listinfo/dev>> > > > > > > > > > > > > > > > -- > > > Ben Parees | OpenShift > > > > > > > > > > > > > -- > > Ben Parees | OpenShift > > > -- Ben Parees | OpenShift
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
