Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'restrict' example gives a warning, doesn't change ntp config, on ntp v2.0.1 #101

Closed
BillWeiss opened this issue Sep 30, 2013 · 1 comment

Comments

@BillWeiss
Copy link
Contributor

I've got this input:

class { '::ntp':
  servers  => [ '0.us.pool.ntp.org', '1.us.pool.ntp.org',
                '2.us.pool.ntp.org', '3.us.pool.ntp.org' ],
  restrict => 'restrict 127.0.0.1',
}

And this output:

root@csv5:/etc/puppet# puppet apply /tmp/ntp_test.pp
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Error: "restrict 127.0.0.1" is not an Array.  It looks to be a String at /etc/puppet/modules/ntp/manifests/init.pp:34 on node csv5.clanspum.net
Error: "restrict 127.0.0.1" is not an Array.  It looks to be a String at /etc/puppet/modules/ntp/manifests/init.pp:34 on node csv5.clanspum.net

For good measure, I tried the exact example from the docs (http://forge.puppetlabs.com/puppetlabs/ntp, under "I'd like to make sure I restrict who can connect as well."):

class { '::ntp':
  servers  => [ 'ntp1.corp.com', 'ntp2.corp.com' ],
  restrict => 'restrict 127.0.0.1',
}

Same warning.

This is Debian 7.1, puppet 3.3.0 from your repo, and version 2.0.1 of the ntp module installed from the forge via librarian-puppet.

@apenney
Copy link
Contributor

apenney commented Sep 30, 2013

Thanks for catching this, totally my fault. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants