Description of problem: DeploymentConfig triggers for ConfigChange are not trigger when DC is updated, in all cases. Version-Release number of selected component (if applicable): 3.2.1 How reproducible: Undetermined. Steps to Reproduce: $ oc get dc > NAME REVISION REPLICAS TRIGGERED BY > cdvr 8 1 config,image(cdvr:7ebf9ee204dbfc36f66d630450c4aa634424de06) > cdvv 10 1 config,image(cdvv:ca86988c567af5a46212044578010a17a949d73c) $ oc edit dc cdvv > deploymentconfig "cdvv" edited $ oc get dc > NAME REVISION REPLICAS TRIGGERED BY > cdvr 8 1 config,image(cdvr:7ebf9ee204dbfc36f66d630450c4aa634424de06) > cdvv 10 1 config,image(cdvv:ca86988c567af5a46212044578010a17a949d73c) $ --> diff cdvv.{before,after}.yaml ## Changes made during `oc edit`. 14c14 < resourceVersion: "11973946" --- > resourceVersion: "12038161" 29c29 < cpu: 100m --- > cpu: 110m 32c32 < cpu: 100m --- > cpu: 110m 55c55 < value: sdfsdf --- > value: sdfsRXRXR 84c84 < cpu: 100m --- > cpu: 110m 87c87 < cpu: 100m --- > cpu: 110m Actual results: Changes are not seen when resource values are updated. Expected results: Changes made to anything under spec.template should trigger a config change. Additional info: http://post-office.corp.redhat.com/archives/aos-devel/2016-September/msg00406.html
*** This bug has been marked as a duplicate of bug 1375820 ***