Bug 1794813

Summary: [buildcop] release-openshift-origin-installer-e2e-aws-upgrade-4.1-stable-to-4.1-nightly failing on: error waiting for deployment \"dp\" to match expectation
Product: OpenShift Container Platform Reporter: Cesar Wong <cewong>
Component: kube-controller-managerAssignee: Maciej Szulik <maszulik>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: aos-bugs, bparees, mfojtik
Target Milestone: ---   
Target Release: 4.2.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1796017 (view as bug list) Environment:
Last Closed: 2020-02-24 16:52:45 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:
Bug Depends On: 1796017    
Bug Blocks:    

Description Cesar Wong 2020-01-24 18:28:25 UTC
Description of problem:

e2e upgrade test fails for release 4.1 on

fail [k8s.io/kubernetes/test/e2e/upgrades/apps/deployments.go:166]: Expected error:
    <*errors.errorString | 0xc0003fbf30>: {
        s: "error waiting for deployment \"dp\" status to match expectation: deployment status: v1.DeploymentStatus{ObservedGeneration:3, Replicas:2, UpdatedReplicas:2, ReadyReplicas:2, AvailableReplicas:2, UnavailableReplicas:0, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:\"Progressing\", Status:\"True\", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63715480704, loc:(*time.Location)(0x90bdf20)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63715480680, loc:(*time.Location)(0x90bdf20)}}, Reason:\"NewReplicaSetAvailable\", Message:\"ReplicaSet \\\"dp-57cc5d77b4\\\" has successfully progressed.\"}, v1.DeploymentCondition{Type:\"Available\", Status:\"True\", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63715482612, loc:(*time.Location)(0x90bdf20)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63715482612, loc:(*time.Location)(0x90bdf20)}}, Reason:\"MinimumReplicasAvailable\", Message:\"Deployment has minimum availability.\"}}, CollisionCount:(*int32)(nil)}",
    }
   error waiting for deployment "dp" status to match expectation: deployment status: v1.DeploymentStatus{ObservedGeneration:3, Replicas:2, UpdatedReplicas:2, ReadyReplicas:2, AvailableReplicas:2, UnavailableReplicas:0, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63715480704, loc:(*time.Location)(0x90bdf20)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63715480680, loc:(*time.Location)(0x90bdf20)}}, Reason:"NewReplicaSetAvailable", Message:"ReplicaSet \"dp-57cc5d77b4\" has successfully progressed."}, v1.DeploymentCondition{Type:"Available", Status:"True", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63715482612, loc:(*time.Location)(0x90bdf20)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63715482612, loc:(*time.Location)(0x90bdf20)}}, Reason:"MinimumReplicasAvailable", Message:"Deployment has minimum availability."}}, CollisionCount:(*int32)(nil)}
not to have occurred

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-stable-to-4.1-nightly/9

Version-Release number of selected component (if applicable):
4.1.z

How reproducible:
e2e upgrade test failure

Steps to Reproduce:
Run release-openshift-origin-installer-e2e-aws-upgrade-4.1-stable-to-4.1-nightly test

Actual results:
test fails

Expected results:
test passes

Additional info:

Comment 1 Maciej Szulik 2020-01-29 12:16:44 UTC
Fix in https://github.com/openshift/origin/pull/24474

Comment 3 Tomáš Nožička 2020-02-04 15:12:54 UTC
*** Bug 1788324 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2020-02-24 16:52:45 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-2020:0460