[release-4.21] OCPBUGS-99756: increase catalog HTTP client timeout from 10s to 5m#773
Conversation
…t from 10s to 5m The 10-second timeout was too aggressive for large catalog responses. Increase it to 5 minutes to avoid timeouts when fetching catalogs. Signed-off-by: Todd Short <tshort@redhat.com>
Backport of upstream #2674. In HA topology (replicas=2), the old catalogd serverutil used OnlyServeWhenLeader=true: the non-leader pod bound the TCP port via net.Listen so the OS accepted connections, but no HTTP server was running. Operator-controller hit the non-leader ~50% of the time and the connection hung silently. With the HTTP client timeout raised to 5m (OCPBUGS-92037), this hang lasted the full 5 minutes instead of 10s, causing catalog caches to never be populated within test windows. Fix: - catalogd serverutil: switch to NeedLeaderElection=false so all pods serve HTTP; non-leaders return 404 (empty local cache) instead of hanging. Register a readiness check so the pod is excluded from endpoints until the server is ready. - client.go: do not cache non-200 responses; return the error directly so the next reconcile retries a fresh HTTP request and eventually hits the leader. Upstream: operator-framework/operator-controller#2674 Signed-off-by: Todd Short <tshort@redhat.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/approve |
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-99298 has been cloned as Jira Issue OCPBUGS-99756. Will retitle bug to link to clone. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-99756, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, rashmigottipati, tmshort The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/jira refresh |
|
@tmshort: This pull request references Jira Issue OCPBUGS-99756, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/jira refresh |
|
@tmshort: This pull request references Jira Issue OCPBUGS-99756, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@tmshort: This pull request references Jira Issue OCPBUGS-99756, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
This is an automated cherry-pick of #768
/assign tmshort