Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #6309

Closed
Open
Created Feb 13, 2014 by Administrator@rootOwner

init script fails when run from within puppet on RHEL derivatives

Created by: deasmi

When the supplied init script lib/support/init.d/gitlab is run from within puppet it can fail silently due to use of sudo.

Tested on Centos 6.5 but believed to be the case on any RHEL derivative.

After adding debugging to capture the output of the init script running under puppet it transpired that sudo was refusing to run due to the lack of a tty.

On RHEL and derivatives the default /etc/sudoers includes

Defaults requiretty

which prevents this init script working under puppet.

Commenting this line out makes everything work as expected.

Given that init scripts are typically/always run by root wouldn't using su be a safe alternative in this instance ?

Assignee
Assign to
Time tracking