Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1444544

Summary: ImageChange Trigger not triggering new deploy pods after a successful build
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: openshift-controller-managerAssignee: Michal Fojtik <mfojtik>
Status: CLOSED DUPLICATE QA Contact: zhou ying <yinzhou>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: aos-bugs, ghyde
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-24 15:01:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
reproducer script none

Description Miheer Salunke 2017-04-22 05:18:35 UTC
Created attachment 1273367 [details]
reproducer script

Description of problem:

During my testing, I discovered that the container image and "lastTriggeredImage" are updating to the latest image after each successful build, even though a deployment isn't being started.

Script to reproduce described behavior.


Version-Release number of selected component (if applicable):
OCP 3.3.0

How reproducible:
Always

Steps to Reproduce:
1.run the attached script
2.
3.

Actual results:
ImageChange Trigger not triggering new deploy pods after a successful build

Expected results:

ImageChange Trigger shall trigger deployment of new pods after a successful build

Additional info:

Comment 1 Garrett Hyde 2017-04-24 15:01:33 UTC

*** This bug has been marked as a duplicate of bug 1444545 ***