-
Notifications
You must be signed in to change notification settings - Fork 237
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
Failed to parse template ssh/sshd_config.erb (undefined method) #26
Comments
Do you set any additional options? |
Use it like this: ` sshd configurationclass { 'ssh::server': |
I'm experiencing the same issue when using the options. Any updates on this. |
Can you verify, if this error occurs without setting any additional options? What version of Puppet have you running? |
@jgornick Can you post your settings, too? |
I'm experiencing the same issue when using the options: sshd configurationclass { 'ssh::server': Error message: |
@saz Configuration and details below:
OS: Ubuntu 12.04.4 |
Does this error occur with puppet running under ruby 1.8.7? |
@saz I am running ruby 1.8.7 on Ubuntu 12.04. |
I have the same issue using puppet 2.7 and ruby 1.8.7 on debian wheezy. |
It seems that this problem only occurs on ruby 1.8.7. I'm not sure, why this is happening but I'll investigate it further and will write a test to make sure it's working on ruby 1.8.7 and 1.9 |
Does this error still occur with the newest release 2.3.3? |
No, it isn't. Solved for me! |
@saz Do you (want to) officially support ruby 1.8.7. |
I'm trying to keep the module working on ruby >=1.8.7 with puppet >=2.7 |
FYI: I've improved the spec test, which seems to suggest, that it's working on 1.8.7 again. |
This is working great for me now on RHEL 6. Thanks so much, and thanks for all your effort maintaining this (and other) modules. |
getting this on Windows client - is the fix a updated Ruby for windows as well?
... |
v2.3.1 seems to have a (fatal) problem with sshd_config.erb (or what's being input to it). A casual glance didn't explain it to me.
The text was updated successfully, but these errors were encountered: