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

using log_prefix seems to result in error on second puppet run #148

Closed
dkindred opened this issue Apr 9, 2013 · 3 comments
Closed

using log_prefix seems to result in error on second puppet run #148

dkindred opened this issue Apr 9, 2013 · 3 comments

Comments

@dkindred
Copy link

dkindred commented Apr 9, 2013

If we have the following

class rcac_firewall::post_accept_all {

firewall { '975 log test':
    state      => 'NEW',
    log_level  => 'debug',
    log_prefix => 'iptables A: ',
    jump       => 'LOG'
}

...
}

On the first puppet run the rule is inserted ok... however, on the second
run we get some errors like this:


info: Applying configuration version '1365457738'
err: /Firewall[975 log test]/log_level: change from iptables A: to 7 failed: The iptables provider can not handle attribute log_level at /etc/puppet/modules/rcac_firewall/manifests/post_accept_all.pp:8
err: /Firewall[975 log test]/log_prefix: change from 7 to iptables A: failed: The iptables provider can not handle attribute log_prefix at /etc/puppet/modules/rcac_firewall/manifests/post_accept_all.pp:8
notice: Finished catalog run in 18.76 seconds


If it is of interest, this is puppet version 2.7.21 running under RHEL 6.3.

@joejulian
Copy link
Contributor

@dkindred can you please test against master

@dkindred
Copy link
Author

This appears to be fixed now (tested against version 0.4.0).

Thanks!

@chelnak
Copy link
Contributor

chelnak commented Mar 8, 2022

Hello! We are doing some house keeping and noticed that this issue has been open for a long time.

We're going to close it but please do raise another issue if the issue still persists. 😄

@chelnak chelnak closed this as completed Mar 8, 2022
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

3 participants