Bug 2305324

Summary: 20240813 is available
Product: [Fedora] Fedora Reporter: Xose Vazquez Perez <xose.vazquez>
Component: microcode_ctlAssignee: Eugene Syromiatnikov <esyr>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: esyr
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: microcode_ctl-2.1-64.fc42 microcode_ctl-2.1-61.2.fc40 microcode_ctl-2.1-58.2.fc39 microcode_ctl-2.1-64.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-08-29 15:35:02 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:

Description Xose Vazquez Perez 2024-08-16 15:04:12 UTC
Changelog: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240813

Reproducible: Always

Comment 1 Fedora Update System 2024-08-29 15:30:49 UTC
FEDORA-2024-8941fc69f5 (microcode_ctl-2.1-64.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8941fc69f5

Comment 2 Fedora Update System 2024-08-29 15:33:27 UTC
FEDORA-2024-dca1b54441 (microcode_ctl-2.1-58.2.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-dca1b54441

Comment 3 Fedora Update System 2024-08-29 15:33:28 UTC
FEDORA-2024-67a38b081a (microcode_ctl-2.1-64.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-67a38b081a

Comment 4 Fedora Update System 2024-08-29 15:35:02 UTC
FEDORA-2024-8941fc69f5 (microcode_ctl-2.1-64.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2024-08-30 01:28:29 UTC
FEDORA-2024-dca1b54441 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-dca1b54441`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-dca1b54441

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-08-30 02:06:08 UTC
FEDORA-2024-5c5c384fa7 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-5c5c384fa7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-5c5c384fa7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-08-30 02:33:45 UTC
FEDORA-2024-67a38b081a has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-67a38b081a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-67a38b081a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-08-31 02:03:59 UTC
FEDORA-2024-5c5c384fa7 (microcode_ctl-2.1-61.2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2024-09-02 01:28:40 UTC
FEDORA-2024-dca1b54441 (microcode_ctl-2.1-58.2.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2024-09-13 20:46:12 UTC
FEDORA-2024-67a38b081a (microcode_ctl-2.1-64.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.