-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-4.15] OCPBUGS-30208: Fix asynccache bugs #13807
base: release-4.15
Are you sure you want to change the base?
Conversation
@TheRealJon: This pull request references Jira Issue OCPBUGS-30208, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In 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. |
42a4c29
to
cc62076
Compare
/jira refresh |
@TheRealJon: This pull request references Jira Issue OCPBUGS-30208, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: In 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. |
Please don't use the merge commits but the actual commits of the PRs |
A cached item might sometimes store the context that it's created with and it might be using it internally. However, the polling logic would cancel this context right after it's finished. This may leave some in-flight hanging requests but it's still better than what we had until now.
The OpenShift-specific well-known endpoint is merely using the OIDC discovery metadata document but it does not follow the standard as the endpoint is actually meant to point at the server that's set up as the IdP for the server, and that's always different from the KAS URL.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stlaz, TheRealJon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@TheRealJon: The following test failed, say
Full PR test history. Your PR dashboard. 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 kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Manual cherry-pick of #13703 and #13647