Details
-
Story
-
Resolution: Done
-
Minor
-
1.7.0.GA
-
False
-
False
-
Release Notes
-
Undefined
Description
When having a persistent build error, for example due to a checksum that does not match, we should stop trying to build after some failed attempts. Any CR update should reset the error counter and restart the build process.
$ oc get pods NAME READY STATUS RESTARTS AGE my-cluster-entity-operator-cfb544f59-6vwqg 3/3 Running 0 105m my-cluster-kafka-0 1/1 Running 0 106m my-cluster-kafka-1 1/1 Running 0 106m my-cluster-kafka-2 1/1 Running 0 106m my-cluster-kafka-exporter-5b458f5f95-g8hqn 1/1 Running 0 103m my-cluster-zookeeper-0 1/1 Running 0 107m my-cluster-zookeeper-1 1/1 Running 0 107m my-cluster-zookeeper-2 1/1 Running 0 107m my-connect-connect-build-5-build 0/1 Error 0 3m53s my-connect-connect-build-6-build 0/1 Error 0 3m6s my-connect-connect-build-7-build 0/1 Error 0 2m19s my-connect-connect-build-8-build 0/1 Error 0 93s my-connect-connect-build-9-build 1/1 Running 0 45s strimzi-cluster-operator-67bfdd6b5b-wnkwf 1/1 Running 0 107m $ oc logs my-connect-connect-build-9-build Caching blobs under "/var/cache/blobs". ... /opt/kafka/plugins/debezium-postgres/debezium-connector-postgres-1.4.0.Final-plugin.tar.gz: FAILED sha512sum: WARNING: 1 computed checksum did NOT match ...
