Red Hat Bugzilla – Bug 1519296
Image triggers don't start Custom Builds in 3.6
Last modified: 2017-12-14 16:02:32 EST
Description of problem: New builds with customStrategy and ImageStreamTag triggers are not started whenever imagestreamtag is updated. See https://github.com/openshift/origin/issues/17074 https://github.com/openshift/origin/pull/17108 Version-Release number of selected component (if applicable): v3.6.0+c4dd4cf How reproducible: Always Steps to Reproduce: 1. Create a new imagestream, add a tag there 2. Create a new buildconfig with customStrategy 3. Set a trigger to the buildconfig to start a new build whenever imagestreamtag is updated 4. Update the tag on imagestream Actual results: No new builds are scheduled Expected results: A new build is scheduled Additional info: This works fine in 3.7 and needs to be backported in 3.6, as it blocks OSBS team to delived chained rebuilds feature
Jim please provide the backport to ose 3.6, thanks.
https://github.com/openshift/ose/pull/946
Can easily fix by updating the role on affected clusters.
verified in released version: openshift v3.6.173.0.83 steps : 1. Create project wewang 2. Create image stream $ oc import-image origin-wenwang --from='docker.io/wewang58/origin-custom-docker-builder' --confirm=true --insecure=true --all=true -n wewang 3. Create custom build $oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/sample-app/application-template-custombuild.json 4. Edit bc with new imagestram and tag "from": { "kind": "ImageStreamTag", "name": "origin-wenwang:latest", "namespace": "wewang" } 5. will trigger new build automatically [root@dhcp-128-91 ~]# oc get builds NAME TYPE FROM STATUS STARTED DURATION ruby-sample-build-1 Custom Git Complete 6 minutes ago 56s ruby-sample-build-2 Custom Git Complete 3 minutes ago 34s
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3438