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

Bug 1790629

Summary:	Cluster fails to install - "Could not update list"
Product:	OpenShift Container Platform	Reporter:	Adam Kaplan <adam.kaplan>
Component:	Cluster Version Operator	Assignee:	Abhinav Dahiya <adahiya>
Status:	CLOSED ERRATA	QA Contact:	Johnny Liu <jialiu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, cdaley, jokerman, lmohanty, vrutkovs, wking, xtian
Target Milestone:	---
Target Release:	4.4.0
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:	2020-05-04 11:24:06 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 Adam Kaplan 2020-01-13 19:13:47 UTC

Description of problem:

CVO fails to complete the installation with error message:
```
level=fatal msg=failed to initialize the cluster: Could not update list \"\" (188 of 529)"
```

This is not a usable or actionable error message. CVO logs do not clearly indicate which operator is failing.

Version-Release number of the following components: 4.4.0

How reproducible: Sometimes

Additional Info:

1. https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/407/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws/2139
2. https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/407/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-image-registry/1467

Comment 1 Vadim Rutkovsky 2020-01-13 19:47:55 UTC

This happened because a List object was added - https://github.com/openshift/cluster-image-registry-operator/pull/407/files#diff-88bbb853bcd5a5fbc188c46767630fad. 

CVO would display object's kind and name. This List doesn't have "name" set, but other than that its a valid object.

Not sure if this is a valid bug though, as its not clear what should CVO show for Lists without names. Perhaps oc should ensure each manifest object should have "name" set?

Comment 2 Adam Kaplan 2020-01-16 22:07:52 UTC

@Vadim this is a bug per the following:

> This is not a usable or actionable error message. CVO logs do not clearly indicate which operator is failing.

This might be a "dev only" issue - we won't ship a version of OpenShift that fails installation on a supported provider/environment. In the case of an unsupported type (`List`), we should log the name of the manifest file the CVO was trying to apply.

Comment 4 Johnny Liu 2020-02-11 08:56:50 UTC

QE can not reproduce this bug. Run a regression, everything is going well. No regression.

Comment 5 Johnny Liu 2020-02-11 08:59:10 UTC

Verification on 4.4.0-0.nightly-2020-02-09-220310

Comment 7 errata-xmlrpc 2020-05-04 11:24:06 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