Bug 1149419 - anaconda creates "/" with wrong permissions 755 instead of 555
Summary: anaconda creates "/" with wrong permissions 755 instead of 555
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Lukáš Nykrýn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-04 21:35 UTC by Christian Stadelmann
Modified: 2015-11-13 14:57 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-13 14:57:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1030691 0 unspecified CLOSED Permissions at root "/ of root filesystem 755 vs 555 2021-02-22 00:41:40 UTC

Internal Links: 1030691

Description Christian Stadelmann 2014-10-04 21:35:08 UTC
Description of problem:
after installation of F21 Alpha "/" has permissions 755. It should have 555.
The package "filesystem" responsible for fs permissions tries to do it right so it seems like anaconda or something else does it wrong.

Additional info:
Similiar bug for RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=1149374

Comment 1 David Shea 2014-10-06 13:48:18 UTC
Please attach the log files from the installation as individual, text/plain attachments. They are available in /tmp in the install environment and copied to /var/log/anaconda in the installed system.

Also, which installation media are you using? (server/workstation/etc). This is working fine for me with both the Server and Workstation installs.

Comment 2 David Shea 2014-10-06 14:08:52 UTC
I take that back. The permissions are being modified after booting into the installed system. / (or rather, /sysroot) is still 0555 just before dracut pivots into the new root, so maybe systemd is modifying the permissions.

Comment 3 David Shea 2014-10-06 14:38:45 UTC
Booting a fresh install into emergency.target, / still has 0555, but booting into rescue.target / has been modified to 0755

Comment 4 Zbigniew Jędrzejewski-Szmek 2014-10-06 15:07:10 UTC
fedora-import-state.service is the culprit. Argh, initscripts!

Comment 5 Jan Synacek 2014-10-07 06:08:01 UTC
Why is this in POST? Do you have a link to an upstream commit fixing the issue?

Comment 7 Fedora End Of Life 2015-11-04 15:53:59 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 8 Christian Stadelmann 2015-11-13 14:57:38 UTC
This issue is not present any more on F23. closing.


Note You need to log in before you can comment on or make changes to this bug.