-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
erlang_cookie detection was better when NOT facter based #94
Comments
To sum it up; using puppet 2.7.22-1puppetlabs1, the custom fact rabbitmq_erlang_cookie seems to be not available to the client so if |
Before I start digging into this I just want to check the very obvious case of making sure pluginsync is enabled for your 2.7 clients, right? |
confirmed, pluginsync is on: info: Retrieving plugin |
Urgh, so embarrassing - #97 fixes this and I'll merge it tomorrow as I'm about to head out of the door. Sorry about this. I'm going to add spec tests for the fact as soon as I can get them to work properly! |
no need to be embarrassed. :) after merging your commit I received the error: err: Failed to apply catalog: Could not find dependency Exec[wipe_db] for File[erlang_cookie] at /etc/puppet/modules/rabbitmq/manifests/config.pp:87 I assume the exec is never executed/processed when the if statement evaluates to true so you end up with this catch 22. I just removed the require. |
I'll dig into this today, I'm working through this with a cold and conjunctivitis so hang in there while I stumble around and fix it up. :) |
This should be fixed now in master. |
the new erlang_cookie change detection is based on a facter
...which is not covered by an rspec btw (I'm trying to, any help is welcome)
seems to lead a continuous un-needed erlang/rabbitmq db deletion
based on the feedback from my colleagues,
the previous implementation "file based" seems to be preferred and more portable across puppet versions
The text was updated successfully, but these errors were encountered: