Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

Error: Failed to apply catalog: Could not find schedule always #62

Closed
santoroj opened this issue Mar 8, 2019 · 1 comment
Closed

Error: Failed to apply catalog: Could not find schedule always #62

santoroj opened this issue Mar 8, 2019 · 1 comment

Comments

@santoroj
Copy link

santoroj commented Mar 8, 2019

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 5.5.6
  • Ruby: 2.5.0
  • Distribution: centos
  • Module version: 0.8.2

How to reproduce (e.g Puppet code you use)

class:
class os_build::l1::hosts{
notify {"*** Applying ${name} ***":}
contain system::hosts
}

hieradate:

system::hosts:
puppet:
ensure: 'present'
ip: "10.0.0.3"
host_aliases: []

Code I've had to change to get this working is to comment out were there is "sys_schedule" as shown below

class system::hosts (
$config = undef,
# $sys_schedule = 'always',
) {
$defaults = {
ensure => 'present',
# schedule => $sys_schedule,
}
if $config {
create_resources(host, $config, $defaults)
}
else {
$hiera_config = hiera_hash('system::hosts', undef)
if $hiera_config {
create_resources(host, $hiera_config, $defaults)
}
}
}

What are you seeing

The following error message is displayed:
Error: Failed to apply catalog: Could not find schedule always

What behaviour did you expect instead

Entries added to /etc/hosts

Output log

Error: Failed to apply catalog: Could not find schedule always

Any additional information you'd like to impart

@santoroj
Copy link
Author

santoroj commented Mar 8, 2019

Sorry - miss understanding on how the module worked. not need to for this ticket - closing

@santoroj santoroj closed this as completed Mar 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant