-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 1862113: bump RHCOS images for CVE-2020-10713 #3985
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 1862113: bump RHCOS images for CVE-2020-10713 #3985
Conversation
|
@miabbott: This pull request references Bugzilla bug 1862113, 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 kubernetes/test-infra repository. |
|
|
/hold While we've tested that booting this RHCOS version via qemu using Secure Boot is successful, there are reports of problems booting with the grub2 mitigation in place - https://bugzilla.redhat.com/show_bug.cgi?id=1861977 I'm going to tentatively hold this until we have more confidence |
|
Confirming the failure to boot via secure boot. |
The mitigation path for OCP customers is to reprovision nodes, so we should bump the boot images on the installer as well.
|
/unhold The latest RHCOS builds include the fixed |
|
|
|
/retest |
|
/test e2e-azure |
|
@abhinavdahiya @sdodson Yet another boot image bump in the series for Boot Hole. |
|
/bugzilla refresh |
|
@miabbott: This pull request references Bugzilla bug 1862113, 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 kubernetes/test-infra repository. |
|
/test e2e-metal |
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson 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 |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
4 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. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@miabbott: The following tests failed, say
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/test-infra repository. I understand the commands that are listed here. |
|
@miabbott: All pull requests linked via external trackers have merged: . Bugzilla bug 1862113 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
…ubelet erroring out with "No authentication method configured" Refer to https://bugzilla.redhat.com/show_bug.cgi?id=1926558. After openshift#4604 landed in 4.4, the multi-arch CI runs started failing because the hyperkube package was old. This was not an issue for x86 as the rhcos images were bumped for a CVE (openshift#3985), resulting in a newer hyperkube package which did not have this issue with the kubelet erroring out on `anonymous-auth=false` These are the builds that were closest in parity to x86: https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4-s390x/44.82.202011122341-0/s390x/meta.json for s390x https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4-ppc64le/44.82.202012010439-0/ppc64le/meta.json for ppc64le
The mitigation path for OCP customers is to reprovision nodes, so we
should bump the boot images on the installer as well.