-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.14.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
Rejected
-
Toasty OLM Sprint 254, Umbridge OLM Sprint 255
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The manual catalog source restart worked after waiting for a long in an unhealthy state which turned out to be the OLM catalog operator not reconciling.
From OLM catalog operator logs we can see below error:
-------------------------------------------------------------------------------------------
E0426 15:07:42.931603 1 queueinformer_operator.go:319] sync "ibm-data-cataloging" failed: bundle unpacking failed with an error: jobs.batch "dc962230623af77a53780578121ade80a5d9ee8891358c1e3fcfd7e700791ab" already exists From OLM catalog operator logs we can see below error:
-------------------------------------------------------------------------------------------
When we look for a job or config map with that name it turns out that indeed it already exists and belongs to a different operator unpack
---------------------------------------------------------------------------------------
$ oc get jobs -A |grep -i dc962230623af77a53780578121ade80a5d9ee8891358c1e3fcfd7e700791ab
openshift-marketplace dc962230623af77a53780578121ade80a5d9ee8891358c1e3fcfd7e700791ab 1/1 38s 2d$ oc get configmap -A |grep -i dc962230623af77a53780578121ade80a5d9ee8891358c1e3fcfd7e700791ab
openshift-marketplace dc962230623af77a53780578121ade80a5d9ee8891358c1e3fcfd7e700791ab 15 2d
----------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
kind: ConfigMap
apiVersion: v1
metadata:
annotations:
olm.contentEncoding: gzip+base64
olm.sourceImage: 'registry.redhat.io/amq-streams/strimzi-operator-bundle@sha256:1346dcee82f2120bd2af22be9f041e057bdc32f9ad1c3ef717d599ba6519faeb'
operators.operatorframework.io.bundle.channel.default.v1: stable
operators.operatorframework.io.bundle.channels.v1: 'stable,amq-streams-2.x,amq-streams-2.4.x'
operators.operatorframework.io.bundle.manifests.v1: manifests/
operators.operatorframework.io.bundle.mediatype.v1: registry+v1
operators.operatorframework.io.bundle.metadata.v1: metadata/
operators.operatorframework.io.bundle.package.v1: amq-streams <<<<<<<<<<<<-----------------------
-------------------------------------------------------------------------------------------------------
that looks like a bug in OLM at the time of generating and assigning unique names to the unpack jobs
Version-Release number of selected component (if applicable):
OpenShift 4.14
How reproducible:
Happened on several installed operators
Steps to Reproduce:
1.
2.
3.
Additional info:
This may be related to https://issues.redhat.com/browse/OCPBUGS-31479
- duplicates
-
-
- Closed
-