RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1348987 - bash[791]: /usr/bin/bash: /sys/devices/system/cpu/microcode/reload: No such file or directory
Summary: bash[791]: /usr/bin/bash: /sys/devices/system/cpu/microcode/reload: No such f...
Keywords:
Status: CLOSED DUPLICATE of bug 1307179
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: microcode_ctl
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Rachel Sibley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-22 12:53 UTC by Brian J. Murrell
Modified: 2016-06-29 12:58 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 12:58:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Brian J. Murrell 2016-06-22 12:53:31 UTC 
Description of problem:
systemctl status microcode.service reports the service failed

Version-Release number of selected component (if applicable):
microcode_ctl-2.1-12.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot up a system without a /sys/devices/system/cpu/microcode/reload handle

Actual results:
The microcode.service until file will fail to load

Expected results:
Should boot cleanly

Additional info:
# systemctl status microcode.service
● microcode.service - Load CPU microcode update
   Loaded: loaded (/usr/lib/systemd/system/microcode.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2016-06-20 20:51:12 EDT; 1 day 11h ago
 Main PID: 791 (code=exited, status=1/FAILURE)

Jun 20 20:51:09 server.interlinx.bc.ca systemd[1]: Starting Load CPU microcode update...
Jun 20 20:51:09 server.interlinx.bc.ca bash[791]: /usr/bin/bash: /sys/devices/system/cpu/microcode/reload: No such file or directory
Jun 20 20:51:12 server.interlinx.bc.ca systemd[1]: microcode.service: main process exited, code=exited, status=1/FAILURE
Jun 20 20:51:12 server.interlinx.bc.ca systemd[1]: Failed to start Load CPU microcode update.
Jun 20 20:51:12 server.interlinx.bc.ca systemd[1]: Unit microcode.service entered failed state.
Jun 20 20:51:12 server.interlinx.bc.ca systemd[1]: microcode.service failed.

Surely this unit could be more intelligent about that missing capability (/sys/devices/system/cpu/microcode/reload) and not cause the unit to fail.
Comment 2 Petr Oros 2016-06-29 12:58:27 UTC 

*** This bug has been marked as a duplicate of bug 1307179 ***
Note You need to log in before you can comment on or make changes to this bug.