Bug 1378724

Summary:	Unable to collect any debug info in pre-shutdown and shutdown shell
Product:	[Fedora] Fedora	Reporter:	Oleg Samarin <osamarin68>
Component:	selinux-policy	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dominick.grift, dracut-maint-list, dwalsh, harald, jonathan, lvrabec, mgrepl, plautrba, pmoore, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 17:35:45 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:

Description Oleg Samarin 2016-09-23 08:23:39 UTC

Description of problem:

I have to collect dmesg for debugging a shutdown sequence in a shutdown shell with rd.break=shutdown kernel option.

But I have access to neither dmesg nor to copying files anywehere in the persistent filesystems

1. When I run dmesg I receive

dmesg: read kernel buffer failed: Permission denied

2. When I try to store any file (ex. /run/initramfs/rdsosreport.txt) to the 
/boot filesysyem, I receive the message

cp: cannot create regular file '/tmp/boot/rdsosreport.txt': Permission denied


Version-Release number of selected component (if applicable):

dracut-044-20.fc24.x86_64
kernel-4.7.4-200.fc24.x86_64
selinux-policy-3.13.1-191.16.fc24.noarch
selinux-policy-targeted-3.13.1-191.16.fc24.noarch


How reproducible:

Always


Steps to Reproduce:

1. Install F24
2. Boot with the kernel option 'rd.break=shutdown'
3. Shutdown
4. Run 'dmesg'
5. Mount the boot filesystem to /tmp/boot and run
cp /run/initramfs/rdsosreport.txt /tmp/boot/


Actual results:

'Permission denied' at the steps 4 and 5


Expected results:
4. The contents of dmesg
5. Capability of saving any files to /bott


Additional info:

Booting with 'enforcing=0' kernel option is not acceptable for debugging because some debugged issues themself relate to selinux. 

So I'd prefer to have precise selinux policies allowing access to dmesg and writing to /boot in the shutdown shell.

Comment 1 Harald Hoyer 2016-10-12 12:09:01 UTC

reassigning to selinux-policy for advise.

Comment 2 Fedora End Of Life 2017-07-25 23:12:10 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 17:35:45 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.