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

Bug 1804937

Summary: [4.4.0] ocm-o reports "Progressing=False" while upgrade is in progress
Product: OpenShift Container Platform Reporter: Adam Kaplan <adam.kaplan>
Component: openshift-controller-managerAssignee: Adam Kaplan <adam.kaplan>
Status: CLOSED ERRATA QA Contact: wewang <wewang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, mfojtik, wewang
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: devex
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: the operator for openshift-controller-manager reported that it was not progressing, even though a rollout of the controller manager was in progress Consequence: the operator prematurely reports that the controller manager is upgraded and available Fix: report that the operator is progressing until the daemonset for the openshift-controller-manager reports that all updated pods have been scheduled Result: the openshift-controller-manager operator does not prematurely report that its update has completed
 Story Points: ---
Clone Of: 1804434 Environment:
Last Closed: 2020-05-04 11:38:10 UTC Type: ---
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: 1804434    
Bug Blocks:    

Description Adam Kaplan 2020-02-19 22:19:41 UTC 
+++ This bug was initially created as a clone of Bug #1804434 +++

Description of problem:

During upgrade, ocm-o reports `Progressing=False` even though the daemonset for the controller is still upgrading and the latest version is not being reported.


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


How reproducible: Sometimes


Expected results:

The operator should report `Progressing=True` until the daemonset rollout has completed.


Additional info:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1484/pull-ci-openshift-machine-config-operator-master-e2e-gcp-upgrade/1098
Comment 4 wewang 2020-02-27 09:33:57 UTC 
Verified in version:
4.4.0-0.nightly-2020-02-26-185356

STEPS:
1. Update build.config.openshift.io, check when 3 pods are not all running in openshift-controller-manager project, then ocm-o report "Progressing=True"
[wewang@wangwen ~]$ oc get co -w |grep "openshift-controller-manager"

openshift-controller-manager               4.4.0-0.nightly-2020-02-26-185356   True        True          False      9h
openshift-controller-manager               4.4.0-0.nightly-2020-02-26-185356   True        True          False      9h
openshift-controller-manager               4.4.0-0.nightly-2020-02-26-185356   True        True          False      9h
openshift-controller-manager               4.4.0-0.nightly-2020-02-26-185356   True        True          False      9h
openshift-controller-manager               4.4.0-0.nightly-2020-02-26-185356   True        False         False      9h  # 3 pods are running
Comment 5 wewang 2020-02-27 09:38:29 UTC 
FYI job passed:https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1514/pull-ci-openshift-machine-config-operator-master-e2e-gcp-upgrade/1195
Comment 7 errata-xmlrpc 2020-05-04 11:38:10 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:0581