Bug 1235233
Summary: | Still seeing log entries for "Failed to reset devices.list on /machine.slice: Invalid argument" with systemd-208-20.el7_1.5 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Devin Henderson <devin> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.1 | CC: | fsumsal, gwysu, igeorgex, jscotka, lnykryn, systemd-maint-list |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | systemd-219-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 15:07:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Devin Henderson
2015-06-24 11:07:41 UTC
To be more specific, this is what shows up in journalctl every 10 minutes. This is the same behavior I was seeing prior to the 208-20.el7_1.5 systemd update. Jun 24 05:10:01 localhost systemd[1]: Created slice user-0.slice. Jun 24 05:10:01 localhost systemd[1]: Starting Session 24 of user root. Jun 24 05:10:01 localhost systemd[1]: Started Session 24 of user root. Jun 24 05:10:01 localhost systemd[1]: Failed to reset devices.list on /machine.slice: Invalid argument Jun 24 05:10:01 localhost systemd[1]: Starting Session 23 of user root. Jun 24 05:10:01 localhost systemd[1]: Started Session 23 of user root. Jun 24 05:10:01 localhost systemd[1]: Failed to reset devices.list on /machine.slice: Invalid argument Damn, I have missed one more patch. This will be definitely fixed in 7.2 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://rhn.redhat.com/errata/RHBA-2015-2092.html |