Bug #587

The crontab provider breaks when ENV[USER] is not set

Added by Luke Kanies almost 5 years ago. Updated almost 5 years ago.

Status:Closed Start date:
Priority:High Due date:
Assignee:Luke Kanies % Done:

0%

Category:-
Target version:0.25.0
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 0

Description

I thought this environment variable was guaranteed by the shell, but it is at least lacking when running under cron.daily and is at least possibly lacking other times. When this is unset, the ParsedFile type breaks, because it requires a default target in order to function.

History

Updated by Tim Stoop almost 5 years ago

Should this default to a user or simply refuse to run when no user is set or what?

Updated by Luke Kanies almost 5 years ago

  • Status changed from 1 to Closed
  • 7 set to fixed

Fixed in r2403.

Also available in: Atom PDF