Newbie
Problem:
I think I am passing yaml correctly from foreman but puppet/cron module 1.3.1 not doing anything with it.
Expected outcome:
cron module in puppet creates cron files.
Foreman and Proxy versions:
1.22.0
Foreman and Proxy plugin versions:
Other relevant data:
I am setting via yaml host group parameters the following but cron module not doing anything with it. I have added the class cron to the host group.
Name
cron::job
yaml
Value
junk:
command: who
minute: 0
hour: 0
date: "*"
month: "*"
weekday: "*"
user: root
environment:
- MAILTO=root
- PATH="/usr/bin:/bin"
description: Test Cron
Running node.rb generates what I think is properly formatted
Parameters:
snip
cron::job:
junk:
command: who
minute: 0
hour: 0
date: "*"
month: "*"
weekday: "*"
user: root
environment:
- MAILTO=root
- PATH="/usr/bin:/bin"
description: Test Cron
Classes:
cron:
When I put code in puppet init.pp it runs correcly but it is not doing anything with the foreman setting.
init.pp (to test module is working)
node default {
}
node 'test-sensor.ensco.win' {
cron::job { 'mysqlbackup':
minute => '40',
hour => '2',
date => '*',
month => '*',
weekday => '*',
user => 'root',
command => 'mysqldump -u root mydb',
environment => [ 'MAILTO=root', 'PATH="/usr/bin:/bin"', ],
description => 'Mysql backup',
}
}
I have a few other modules ntp, sudo, pam, etc working but they are all using parameters foreman found with an import. this is the first time i had to use host group parameters because foreman did not find cron::job since it is not a class in the package.
Any idea what I am doing wrong? I looked in log files but don’t see anything related to it. it logs the puppet code in init.pp but jut completely ignores the foreman setting. puppet agent --test --debug makes not mention of the yaml / hierra data.
logs