Bug 1264979
Summary: | poweroff: Failed to execute operation: Access denied | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dr. David Alan Gilbert <dgilbert> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-22 09:55:26 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
Dr. David Alan Gilbert
2015-09-21 19:29:31 UTC
Actually, it's worse than this; sudo poweroff doesn't help in this case either: [41864.433658] audit: type=1107 audit(1442863804.802:1224): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { start } for auid=1000 uid=0 gid=0 path="/usr/lib/systemd/system/poweroff.target" cmdline="poweroff" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=system_u:object_r:power_unit_file_t:s0 tclass=service exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?' Failed to start poweroff.target: Access denied (I'm reasonably sure I've had it work once after I upgraded to f23?!) Can you verify that also selinux-policy is upgraded to version from F23? (In reply to Michal Sekletar from comment #2) > Can you verify that also selinux-policy is upgraded to version from F23? [dgilbert@dgilbert-t530 ~]$ rpm -qa selinux-policy selinux-policy-3.13.1-147.fc23.noarch looks like it. Dave I believe this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1264051. Forced reboot should work around this. *** This bug has been marked as a duplicate of bug 1264051 *** |