Bug 1849061
Summary: | [rhel-7.4.z] Enable SNB-EP caveat by default | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
Component: | microcode_ctl | Assignee: | Eugene Syromiatnikov <esyr> |
Status: | CLOSED ERRATA | QA Contact: | Jeff Bastian <jbastian> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 7.9 | CC: | esyr, pvlasin, skozina |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | microcode_ctl-2.1-22.32.el7_4 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1846023 | Environment: | |
Last Closed: | 2020-06-30 12:11:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1846023 | ||
Bug Blocks: |
Description
RAD team bot copy to z-stream
2020-06-19 14:23:15 UTC
Verified with microcode_ctl-2.1-22.32.el7_4. Sandy Bridge EP microcode was updated automatically (there was no need for a "force" file since it's no longer blacklisted). The failed tasks are due to the blacklisted microcode for the CPU models due to the potential for a system freeze at boot. The failure is because the system is not running the latest version of the microcode due to the blacklist, thus the failure is expected and it means the blacklist is working. When the microcode update was forced, the 06-4e-03 system did hang on boot and I had to interrupt grub and add dis_ucode_ldr to get the system to boot and finish running the job. The /sys/devices/system/cpu/vulnerabilities/srbds file reports "Mitigation: Microcode" on systems with affected CPUs and successful microcode updates. https://beaker.engineering.redhat.com/jobs/4378876 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:2771 |