Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1386652

Summary:	No documentation about systemd in chroot
Product:	Red Hat Enterprise Linux 7	Reporter:	Andreas Bleischwitz <ableisch>
Component:	doc-System_Administrators_Guide	Assignee:	Maxim Svistunov <msvistun>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.0	CC:	msekleta, rhel-docs, rvykydal
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-11 07:59:54 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 Andreas Bleischwitz 2016-10-19 11:46:45 UTC

Description of problem:
systemd prevents the start/stop of any service when started in a chroot environment which is nowhere mentioned in the RHEL7 documentation.

Version-Release number of selected component (if applicable):
Any version starting with RHEL7

How reproducible:
Always

Steps to Reproduce:
1. try to "systemctl start <service>" within a kickstart %post-section
2. realize that it gets denied because of the chroot
3. despreately search for the documentation of this behavior.

Actual results:
Nothing found

Expected results:
find a note/hint that starting services via systemd is not *possible* at all in a chroot.

Additional info: