Bug 1260037

Summary: systemd-nspawn: Failed to create directory /var/lib/mock/fedora-23-x86_64/root//sys/fs/selinux: Read-only file system
Product: [Fedora] Fedora Reporter: Miroslav Suchý <msuchy>
Component: systemdAssignee: systemd-maint
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 26CC: johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:35:39 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 Miroslav Suchý 2015-09-04 09:37:02 UTC
Description of problem:
I get warning from systemd-nspawn:
Failed to create directory /var/lib/mock/fedora-23-x86_64/root//sys/fs/selinux: Read-only file system

Version-Release number of selected component (if applicable):
systemd-219-21.fc22.x86_64

How reproducible:
deterministic

Steps to Reproduce:
1. mock -r fedora-23-x86_64 --new-chroot --shell -vvv
The last command would be probably something like:
/usr/bin/systemd-nspawn -M 8ddcba49b6ac48ceac6eaaf7c0145e9f -D /var/lib/mock/fedora-23-x86_64/root /bin/sh -i -l

Running it over sudo will give you the warning. It looks like error, but nspawn proceed anyway. So it is not fatal.

I have disabled selinux:
$ getenforce 
Disabled

Actual results:
Weird looking error, which scares me.

Expected results:
No error, or some note, that it is fail to ignore it when I have selinux disabled.

Possible duplicate of bug 1226567.

Additional info:

Comment 1 Fedora End Of Life 2016-07-19 20:13:32 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.

Comment 2 Miroslav Suchý 2016-07-27 14:29:30 UTC
Very likely still valid. (I do not have system with disabled selinux on hand right now).

Comment 3 Fedora End Of Life 2017-02-28 09:48:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 4 Fedora End Of Life 2018-05-03 09:08:12 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 5 Fedora End Of Life 2018-05-29 11:35:39 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.

Comment 6 Miroslav Suchý 2018-05-30 10:50:01 UTC
I cannot reproduce it any longer.