-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
quay-v3.10.0
-
False
-
None
-
False
-
-
-
0
Description:
This is a Quay Operator issue found in Quay 3.10, On OCP 4.15(AWS STS) with Cluster wide proxy deploy Quay with Quay Operator was failed, and find the following log in Quay Operator POD logs, and also confirmed from Quay Operator POD can access the target OCP Route API endpoint with Cluster proxy successfully, the problem is Quay Operator can't use the OCP Cluster Proxy to check OCP Route API, pls review this issue.
"2023-12-12T08:38:13Z DEBUG events could not check for `Routes` API: dial tcp 35.76.1.59:443: connect: connection timed out {"type": "Warning", "object": {"kind":"QuayRegistry","namespace":"quay-enterprise","name":"quay","uid":"05f0599d-6599-420f-9c84-47a37ec308c9","apiVersion":"quay.redhat.com/v1","resourceVersion":"43681"}, "reason": "RouteComponentDependencyError"}
Quay Version: 3.10
Confirmed from Quay Operator POD can access the target OCP Route API Endpoint:
OCP Route API IP address:
host api.apps.ci-op-srr9g7kj-e02bc.qe.devcluster.openshift.com api.apps.ci-op-srr9g7kj-e02bc.qe.devcluster.openshift.com has address 35.76.1.59 api.apps.ci-op-srr9g7kj-e02bc.qe.devcluster.openshift.com has address 18.180.210.201
2023-12-12T08:33:37Z INFO controller-runtime.metrics Metrics server is starting to listen {"addr": ":8080"}
2
2023-12-12T08:33:37Z INFO setup starting manager
3
2023-12-12T08:33:37Z INFO starting server {"path": "/metrics", "kind": "metrics", "addr": "[::]:8080"}
4
2023-12-12T08:33:37Z INFO Starting EventSource {"controller": "quayregistry", "controllerGroup": "quay.redhat.com", "controllerKind": "QuayRegistry", "source": "kind source: *v1.QuayRegistry"}
5
2023-12-12T08:33:37Z INFO Starting Controller {"controller": "quayregistry", "controllerGroup": "quay.redhat.com", "controllerKind": "QuayRegistry"}
6
2023-12-12T08:33:37Z INFO Starting EventSource {"controller": "quayregistry", "controllerGroup": "quay.redhat.com", "controllerKind": "QuayRegistry", "source": "kind source: *v1.QuayRegistry"}
7
2023-12-12T08:33:37Z INFO Starting Controller {"controller": "quayregistry", "controllerGroup": "quay.redhat.com", "controllerKind": "QuayRegistry"}
8
2023-12-12T08:33:37Z INFO Starting workers {"controller": "quayregistry", "controllerGroup": "quay.redhat.com", "controllerKind": "QuayRegistry", "worker count": 1}
9
2023-12-12T08:33:37Z INFO Starting workers {"controller": "quayregistry", "controllerGroup": "quay.redhat.com", "controllerKind": "QuayRegistry", "worker count": 1}
10
2023-12-12T08:33:51Z INFO controllers.QuayRegistry begin reconcile {"quayregistry": "quay-enterprise/quay"}
11
2023-12-12T08:33:51Z INFO controllers.QuayRegistry TLS cert/key pair not provided, using default cluster wildcard cert
12
2023-12-12T08:33:51Z INFO controllers.QuayRegistry cluster supports `Routes` API
13
2023-12-12T08:33:52Z INFO controllers.QuayRegistry Detected cluster hostname apps.ci-op-srr9g7kj-e02bc.qe.devcluster.openshift.com
14
2023-12-12T08:38:13Z DEBUG events could not check for `Routes` API: dial tcp 35.76.1.59:443: connect: connection timed out {"type": "Warning", "object": {"kind":"QuayRegistry","namespace":"quay-enterprise","name":"quay","uid":"05f0599d-6599-420f-9c84-47a37ec308c9","apiVersion":"quay.redhat.com/v1","resourceVersion":"43681"}, "reason": "RouteComponentDependencyError"}
15
2023-12-12T08:38:13Z INFO controllers.QuayRegistryStatus quay components conditions reconciled {"quayregistrystatus": {"name":"quay","namespace":"quay-enterprise"}}
16
2023-12-12T08:38:13Z INFO controllers.QuayRegistryStatus quay components conditions reconciled {"quayregistrystatus": {"name":"quay","namespace":"quay-enterprise"}}
17
2023-12-12T08:38:23Z INFO controllers.QuayRegistry begin reconcile {"quayregistry": "quay-enterprise/quay"}
18
2023-12-12T08:38:23Z INFO controllers.QuayRegistry TLS cert/key pair not provided, using default cluster wildcard cert
19
2023-12-12T08:38:23Z INFO controllers.QuayRegistry cluster supports `Routes` API
20
2023-12-12T08:38:24Z INFO controllers.QuayRegistry Detected cluster hostname apps.ci-op-srr9g7kj-e02bc.qe.devcluster.openshift.com
21
2023-12-12T08:42:48Z DEBUG events could not check for `Routes` API: dial tcp 18.180.210.201:443: connect: connection timed out {"type": "Warning", "object": {"kind":"QuayRegistry","namespace":"quay-enterprise","name":"quay","uid":"05f0599d-6599-420f-9c84-47a37ec308c9","apiVersion":"quay.redhat.com/v1","resourceVersion":"45864"}, "reason": "RouteComponentDependencyError"}
22
