sssd missing required directories on netboot image #1813

Closed
travisgroth opened this Issue Feb 17, 2017 · 0 comments

Comments

Projects
None yet
3 participants
@travisgroth

Issue Report

Bug

Container Linux Version

coreos0 ~ # cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1313.0.0
VERSION_ID=1313.0.0
BUILD_ID=2017-02-03-0826
PRETTY_NAME="Container Linux by CoreOS 1313.0.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

Environment

Network Boot VMware and Metal

Expected Behavior

Dropping an sssd.conf and enabling the sssd service is sufficient to have sssd start on boot

Actual Behavior

Three directories must be created before sssd will start. One appears to be for log files, so it may be better to change the base unit file to be non-forking and keep sssd in the foreground to capture output.

Sample drop-in that results in successful sssd start:

[Service]
ExecStartPre=/usr/bin/mkdir -p /var/lib/sss/pipes/private
ExecStartPre=/usr/bin/mkdir -p /var/lib/sss/db
ExecStartPre=/usr/bin/mkdir -p /var/log/sssd

Reproduction Steps

  1. Configure sssd.conf
  2. Enable sssd service
  3. Observe failure messages while trying to start it (must run in debug to see the pipe error)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment