Hide Forgot
Description of problem:When checking the state of cluster operator it shows cluster-image-registry-operator as Updating Unable to apply resources: unable to apply objects: failed to create object *v1.Image, Name=cluster: images.config.openshift.io "cluster" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update v4.0.0-0.148.0.0-dirty oc describe clusteroperator cluster-image-registry-operator Name: cluster-image-registry-operator Namespace: Labels: <none> Annotations: <none> API Version: config.openshift.io/v1 Kind: ClusterOperator Metadata: Creation Timestamp: 2019-01-28T06:19:53Z Generation: 1 Resource Version: 12130 Self Link: /apis/config.openshift.io/v1/clusteroperators/cluster-image-registry-operator UID: b981cce3-22c4-11e9-add3-06c4c3807714 Spec: Status: Conditions: Last Transition Time: 2019-01-28T06:24:54Z Message: Deployment does not exist Status: False Type: Available Last Transition Time: 2019-01-28T06:24:54Z Message: Unable to apply resources: unable to apply objects: failed to create object *v1.Image, Name=cluster: images.config.openshift.io "cluster" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update Status: True Type: Progressing Last Transition Time: 2019-01-28T06:24:54Z Status: False Type: Failing Extension: <nil> Version: v4.0.0-0.148.0.0-dirty Events: <none> oc get crd images.config.openshift.io -o yaml apiVersion: apiextensions.k8s.io/v1beta1 kind: CustomResourceDefinition metadata: creationTimestamp: 2019-01-28T06:19:46Z generation: 1 name: images.config.openshift.io resourceVersion: "6000" selfLink: /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/images.config.openshift.io uid: b5b91d21-22c4-11e9-add3-06c4c3807714 spec: additionalPrinterColumns: - JSONPath: .metadata.creationTimestamp description: |- CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC. Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata name: Age type: date group: config.openshift.io names: kind: Image listKind: ImageList plural: images singular: image scope: Cluster subresources: status: {} version: v1 versions: - name: v1 served: true storage: true status: acceptedNames: kind: Image listKind: ImageList plural: images singular: image conditions: - lastTransitionTime: 2019-01-28T06:19:46Z message: no conflicts found reason: NoConflicts status: "True" type: NamesAccepted - lastTransitionTime: null message: the initial names have been accepted reason: InitialNamesAccepted status: "True" type: Established storedVersions: - v1 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: failed updating state of clusteroperator image-registry Expected results: New installation should show running state instead of updating failed state of cluster operator Additional info:
https://github.com/openshift/cluster-image-registry-operator/pull/181
*** Bug 1671175 has been marked as a duplicate of this bug. ***
No such issue now: Status: Conditions: Last Transition Time: 2019-02-18T08:08:23Z Message: Deployment has minimum availability Status: True Type: Available Last Transition Time: 2019-02-19T03:48:25Z Message: Everything is ready Status: False Type: Progressing Last Transition Time: 2019-02-18T04:12:53Z Status: False Type: Failing Extension: <nil> Related Objects: <nil> Versions: Name: operator Version: v4.0.0-0.174.0.0-dirty Events: <none>
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:0758