Bug 791015 - kickstart chroot environment, runlevel returns unknown
Summary: kickstart chroot environment, runlevel returns unknown
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.2
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-15 23:04 UTC by Dave Sullivan
Modified: 2018-11-28 21:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-16 01:08:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.