Red Hat Bugzilla – Bug 1462131
When new build completed the latest image info not updated to the deploymentconfig
Last modified: 2017-09-26 08:48:47 EDT
Description of problem:
Trigger new build, when the build completed the latest image info updated to the istag, but not updated to deploymentconfig, so no new deploy triggered.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login Openshift and create project;
2. Create app ;
`oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git`
3. After the first build completed, trigger new build, check the istag and deploymentconfig
3. The istag updated with the latest image info, but the deploymentconfig not updated.
3. Should update the deploymentconfig with the latest image info , and trigger new deploy automaticly.
This is probably the same issue as https://github.com/openshift/origin/issues/14725
I can reproduce it. Seems like there is problem with image trigger not seeing the new tag:
I0620 10:02:48.012872 21267 factory.go:185] Image stream "ruby-ex" updated.
I0620 10:02:48.012969 21267 image_trigger_controller.go:342] Started syncing image stream "test/ruby-ex"
I0620 10:02:48.012985 21267 image_trigger_controller.go:344] Finished syncing image stream "test/ruby-ex" (31.571µs)
I0620 10:02:48.013028 21267 image_trigger_controller.go:370] Started syncing resource "deploymentconfigs.apps.openshift.io/test/ruby-ex"
I0620 10:02:48.013085 21267 deploymentconfigs.go:238] Deployment config ruby-ex has not changed
On consequent runs it sometimes succeeds. Seems racy... I will investigate further...
It will also deploy after master is restarted so I am suspecting caches not being synced
PR in place: https://github.com/openshift/origin/pull/14773
Verify this issue on latest OCP:
When image changes will trigger new deployment.