Bug 791015

Summary:	kickstart chroot environment, runlevel returns unknown
Product:	Red Hat Enterprise Linux 6	Reporter:	Dave Sullivan <dsulliva>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-16 01:08:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Sullivan 2012-02-15 23:04:17 UTC

Description of problem:

In RHEL6U2 kickstart chroot environment, /sbin/runlevel command always returns 'unknown' (/var/run/utmp is 0 bytes in chroot), which is causing problem with puppet runs when puppet tries to manage all kinds of redhat services. 

If we replace /sbin/runlevel with a shell script "echo N 3" or replace /var/run/utmp file from an up and running RHEL6 server, to make runlevel command happy, then things are fine. 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Brian Lane 2012-02-16 01:08:27 UTC

This is not a problem with anaconda. The chroot environment is just a chroot and runlevel cannot be expected to run properly from it.