-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Adding a port gets an error the first time #38
Comments
Having the same issue here, were you able to figure it out? |
My terminal returns that the port was already defined when I try to run it again. |
Like I said, it does appear to work, but it reports an error. This only happens the first time it runs, after that, it "detects" that its already there and doesn't run. I am wondering if it has anything to do with SELINUX being disabled on digitalocean? Were you able to reproduce it on other providers? Tommy |
I will try it out on AWS as soon as I get another box spun up I can test On Mon, Dec 21, 2015 at 10:35 AM, Tommy McNeely notifications@github.com
|
@thoopes the problem is for sure selinux is disabled. the semanage utility fails to list things while selinux is disabled and puppet then does not know what to do and fails ugly. this is now documented in the README.md and will possibly worked around by not applying the resources while disabled. |
I am seeing the following error:
With the following puppet code (snippet):
I only get the error the first time it runs, but it does succeed. I haven't really dug into the code yet, but I am seeing this consistently enough (every time recently) that I thought I should report it. :)
NOTE: I am building a CentOS 7 VM (droplet) at Digital Ocean.
The text was updated successfully, but these errors were encountered: