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.9] Bug 2076256: Mitigate multiple CVEs #1432
[release-4.9] Bug 2076256: Mitigate multiple CVEs #1432
Conversation
@coreydaley: This pull request references Bugzilla bug 2076256, 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. |
@coreydaley: This pull request references Bugzilla bug 2076256, 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. |
8db7c57
to
02e59e4
Compare
/assign @adambkaplan @gabemontero @jkhelil @akram |
/assign @jitendar-singh @prietyc123 |
/label backport-risk-assessed |
the e2e-aws-jenkins failure could just be a flake, but it is not something I've typically seen @coreydaley (complaining about an annotation missing on the build) .... there may be an issue with the plugin combination that has broken something on 4.9, and would need to be investigated (where for some things it is easier to build the image from these changes, push them to docker.io or quay.io, and then tag that image into the imagestream). Let's see /retest |
/label cherry-pick-approved |
yeah same error as last time @coreydaley
you are going to need to run an image from these changes in a 4.9 cluster and debug what is going on. |
/hold |
Mitigates: - CVE-2022-29036 - CVE-2022-29041 - CVE-2022-29046 - CVE-2022-29047 - CVE-2022-29048 - CVE-2022-27195 - CVE-2022-27196 Bumps Jenkins version to 2.319.3 to support plugin updates
02e59e4
to
a1970c2
Compare
/bugzilla refresh |
@coreydaley: This pull request references Bugzilla bug 2076256, 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. |
/hold cancel |
/retest-required |
/bugzilla refresh |
@coreydaley: This pull request references Bugzilla bug 2076256, 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. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: coreydaley, jkhelil 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 |
/refresh |
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
@openshift-bot: This pull request references Bugzilla bug 2076256, 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 Recalculating validity in case the underlying Bugzilla bug has changed. |
@openshift-bot: This pull request references Bugzilla bug 2076256, 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 |
@coreydaley: This pull request references Bugzilla bug 2076256, which is valid. 6 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 kubernetes/test-infra repository. |
/retest |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@coreydaley: all tests passed! 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/test-infra repository. I understand the commands that are listed here. |
@coreydaley: All pull requests linked via external trackers have merged: Bugzilla bug 2076256 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. |
ART Request: https://issues.redhat.com/browse/ART-4051 Installed plugins: |
Mitigates: