Detail
Some error messages related to remote servers may occasionally appear in the logs. Examples:olm-operator:
Operation cannot be fulfilled on operators.operators.coreos.com "aerospike-kubernetes-operator.aerospike": the object has been modified; please apply your changes to the latest version and try again
catalog-operator:
E0823 20:06:59.160102 1 queueinformer_operator.go:290] sync "aerospike" failed: error using catalog aerospike-kubernetes-operator-catalog (in namespace aerospike): failed to list bundles: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.79.116.199:50051: connect: no route to host" time:2022-08-23T20:06:59.16027486Z
I0823 20:06:26.545560 1 event.go:282] Event(v1.ObjectReference{Kind:"Namespace", Namespace:"", Name:"aerospike", UID:"43fbef49-4ab9-473b-adb8-b12dd245ddc9", APIVersion:"v1", ResourceVersion:"6611430", FieldPath:""}): type: 'Warning' reason: 'ResolutionFailed' error using catalog aerospike-kubernetes-operator-catalog (in namespace aerospike): failed to list bundles: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.83.34.120:50051: i/o timeout"
packageserver:
time="2022-08-23T20:08:57Z" level=warning msg="error getting stream" action="refresh cache" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 10.79.116.199:50051: connect: no route to host\"" source="{aerospike-kubernetes-operator-catalog aerospike}"