Bug 1921180 - CVO transitions from "Initializing" to "Updating" despite not attempting many manifests
Summary: CVO transitions from "Initializing" to "Updating" despite not attempting many...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.z
Assignee: Jack Ottofaro
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1905221
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-27 17:05 UTC by OpenShift BugZilla Robot
Modified: 2021-03-02 04:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-02 04:48:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-version-operator pull 506 0 None closed Bug 1921180: pkg/cvo/sync_worker.go: Ignore work changes during init 2021-02-18 04:02:43 UTC
Red Hat Product Errata RHBA-2021:0634 0 None None None 2021-03-02 04:48:28 UTC

Comment 2 Johnny Liu 2021-02-18 08:51:42 UTC
Verified this bug with 4.6.0-0.nightly-2021-02-18-050133, PASS.

[root@ip-10-0-27-194 ~]# vi /tmp/version-patch-first-override.yaml
[root@ip-10-0-27-194 ~]# cd /etc/kubernetes/
[root@ip-10-0-27-194 kubernetes]# cat /tmp/version-patch-first-override.yaml
- op: add
  path: /spec/overrides
  value:
  - kind: DaemonSet
    group: apps/v1
    name: cluster-network-operator
    namespace: openshift-cluster-network-operator
    unmanaged: true
[root@ip-10-0-27-194 kubernetes]# export KUBECONFIG=./kubeconfig
[root@ip-10-0-27-194 kubernetes]# oc patch clusterversion version --type json -p "$(cat /tmp/version-patch-first-override.yaml)"
clusterversion.config.openshift.io/version patched
[root@ip-10-0-27-194 kubernetes]#  oc get all -n openshift-cluster-version
NAME                                            READY   STATUS    RESTARTS   AGE
pod/cluster-version-operator-7c747b7b99-nd46k   0/1     Pending   0          5m17s

NAME                               TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
service/cluster-version-operator   ClusterIP   172.30.45.184   <none>        9099/TCP   5m52s

NAME                                       READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/cluster-version-operator   0/1     1            0           5m44s

NAME                                                  DESIRED   CURRENT   READY   AGE
replicaset.apps/cluster-version-operator-6b794bff47   0         0         0       5m44s
replicaset.apps/cluster-version-operator-7c747b7b99   1         1         0       5m17s
[root@ip-10-0-27-194 kubernetes]# crictl ps -a |grep version
de2e88f23c1c6       registry.ci.openshift.org/ocp/release@sha256:8de8b391a3d6c83b050fcb30ce06e430b4f3a7c2ba3dd45e359faccd65372ae5            6 minutes ago       Running             cluster-version-operator         0                   5cd282b8bdb08
[root@ip-10-0-27-194 kubernetes]# crictl logs -f de2e88f23c1c6 2>&1 |grep "Running sync .* in state"
I0218 08:40:48.311691       1 sync_worker.go:513] Running sync 4.6.0-0.nightly-2021-02-18-050133 (force=false) on generation 1 in state Initializing at attempt 1
I0218 08:44:04.144401       1 sync_worker.go:513] Running sync 4.6.0-0.nightly-2021-02-18-050133 (force=false) on generation 1 in state Initializing at attempt 2
I0218 08:47:41.430232       1 sync_worker.go:513] Running sync 4.6.0-0.nightly-2021-02-18-050133 (force=false) on generation 2 in state Initializing at attempt 3

Comment 5 errata-xmlrpc 2021-03-02 04:48: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 (OpenShift Container Platform 4.6.19 bug fix update), 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-2021:0634


Note You need to log in before you can comment on or make changes to this bug.