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
Bug 1906100: use child context to verify payload signature on forced update #493
Conversation
/retest |
/test e2e-agnostic-upgrade |
e20f46d
to
1925f4f
Compare
@jottofar: This pull request references Bugzilla bug 1906100, which is invalid:
Comment 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 kubernetes/test-infra repository. |
1 similar comment
@jottofar: This pull request references Bugzilla bug 1906100, which is invalid:
Comment 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 kubernetes/test-infra repository. |
/test e2e-agnostic |
@jottofar: This pull request references Bugzilla bug 1906100, which is invalid:
Comment 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 kubernetes/test-infra repository. |
/bugzilla refresh |
@wking: This pull request references Bugzilla bug 1906100, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jottofar, wking 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 Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@jottofar: All pull requests linked via external trackers have merged: Bugzilla bug 1906100 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
/cherrypick release-4.6 |
@wking: new pull request created: #504 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 kubernetes/test-infra repository. |
Snuck into the logs with 687686e (pkg/cvo/updatepayload.go: use child context to retrieve payload, 2021-01-07, openshift#493).
When '--force' is specified for an update, create new context with reduced timeout for use in signature verification to allow time to perform update.
The currently used context's timeout is set by SyncWorker Start based on an initial interval of 2 to ~4 minutes modified based on work.State and can therefore range from 2 to ~8 minutes. My testing found that during verify payload it had a 5 to 6 minute deadline. I therefore created a child context with a timeout of half that value when
--force
is specified.