Bug 1623612

Summary: e2e image change trigger test failed
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: MasterAssignee: Michal Fojtik <mfojtik>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas, xxia
Target Milestone: ---   
Target Release: 3.11.z   
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: 2019-04-11 05:38:22 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:

Description Clayton Coleman 2018-08-29 18:06:31 UTC
Deployment config e2e failure

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/18816/pull-ci-origin-e2e-gcp/2997/#featuredeploymentconfig-deploymentconfigs-when-changing-image-change-trigger-conformance-should-successfully-trigger-from-an-updated-image-suiteopenshiftconformanceparallelminimal

failed in 3.11 master

[Feature:DeploymentConfig] deploymentconfigs when changing image change trigger [Conformance] should successfully trigger from an updated image

/tmp/openshift/build-rpms/rpm/BUILD/origin-3.11.0/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:394
Expected error:
    <*errors.errorString | 0xc421a0ce60>: {
        s: "expected latestVersion: 2, got: 1",
    }
    expected latestVersion: 2, got: 1
not to have occurred
/tmp/openshift/build-rpms/rpm/BUILD/origin-3.11.0/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:417

Comment 1 Michal Fojtik 2018-08-29 18:47:25 UTC
Hope-to-be-fix: https://github.com/openshift/origin/pull/20799

Comment 2 Michal Fojtik 2019-03-07 11:25:50 UTC
This should be fixed by https://github.com/openshift/origin/pull/20799

I haven't seen that errors anymore.

Comment 5 errata-xmlrpc 2019-04-11 05:38:22 UTC
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-2019:0636