Bug 1386632

Summary:	ProtectHome=true for bluetooth.service on atomic host gets error=226/NAMESPACE
Product:	[Fedora] Fedora	Reporter:	Patrick Uiterwijk <puiterwijk>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	amigadave, johannbg, lnykryn, msekleta, muadda, pbrobinson, ssahani, s, systemd-maint, 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:	2018-05-29 11:37:20 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:
Bug Depends On:
Bug Blocks:	1269538

Description Patrick Uiterwijk 2016-10-19 10:36:10 UTC

Description of problem:
On systemctl start bluetooth.service, it aborts with code=exited, status=226/NAMESPACE.
Note that /tmp is a symlink to sysroot/tmp due to this being an ostree-based system.

Version-Release number of selected component (if applicable):
systemd-231-9.fc26
bluez-5.41-1.fc26

How reproducible:
Consistent

Steps to Reproduce:
1. Run system based on OSTree
2. systemctl start bluetooth.service

Actual results:
Active: failed (Result: exit-code) 
Main PID: 14706 (code=exited, status=226/NAMESPACE)

Expected results:
Active: active (running)

Additional info:
If I copy bluetooth.service to /etc/systemd/system/bluetooth.service, and modify it to have ProtectHome=read-only, it starts succesfully.

Comment 1 Zbigniew Jędrzejewski-Szmek 2016-10-20 01:55:03 UTC

Pffff, yeah, it's possible. There's been a major restructuring of the namespacing code in systemd-232 (soon to be released). Let's wait for that and see if that changes anything.

Comment 2 Fedora End Of Life 2017-02-28 10:28:21 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 3 Zbigniew Jędrzejewski-Szmek 2017-07-11 05:32:39 UTC

https://github.com/systemd/systemd/pull/6293

Comment 4 Fedora End Of Life 2018-05-03 08:24:26 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:37:20 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.