-
-
Notifications
You must be signed in to change notification settings - Fork 500
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
Duplicate declaration: Apt::Pin[rabbitmq] is already declared #79
Comments
Hi, First thanks for the detailed bug report! I am gearing up to do a rc release of 3.0.0 that completely refactors and rewrites this module. I've made extensive changes to almost all pieces of it so I'd really appreciate it if you could grab the latest version from git (master, that is), and retest. You will need to tweak how you call the class so it's more like: class { 'rabbitmq::repo::apt': class { 'rabbitmq': As I've removed the ::server class completely. I think it should work much better for you with the current version. I'll release a 3.0.0rc into the forge today so you can puppet module install it in future! |
Hey, thanks for the quick response! I just tried running this with the latest master (24ee1de), but am now getting this error:
|
Hmm, this one is weird! debug: Adding relationship from Class[Rabbitmq::Repo::Apt] to Package[rabbitmq-server] with 'before' I just ran the test suite against ubuntu precise and got: Finished in 3 minutes 11.6 seconds So I don't understand what's happening I'm afraid! It must be somehow vagrant specific. |
Ok, so I did a tiny bit more digging, and found an issue (http://projects.puppetlabs.com/issues/7422) that led me to believe that maybe the puppet version Vagrant installs (2.7.19) isn't recent enough. So I installed the latest gem (3.2.3), and also took Vagrant out of the equation by running puppet manually on the VM. Now I'm getting a more expressive error, but still don't know what to do with it. Does this mean anything to you?
|
Interestingly, when I remove the 'delete_guest_user' option, it works… (Still not with puppet 2.7.19 though.) I had to add curl as a dependency, which isn't part of my bare-bones Ubuntu box… manifests/site.pp: package { 'curl':
ensure => present
}
class { 'rabbitmq::repo::apt':
pin => 900,
before => Class['rabbitmq::install']
}
class { 'rabbitmq':
port => '5673',
} Now the output has changed to:
|
I think I know what the issue is, and #75 should fix it. It's failing the spec tests so I've still got a little work to do but the restructuring was causing a dependency issue only when the delete_guest user was set (which annoyingly wasn't showing up in testing). I'll keep working on this PR today and merge it in so you can do some more testing. Annoying to find out about curl, let me have a think about the best way to handle that as I'd like for you to have to do nothing to get this going but include the class. :) |
This should be fixed now if you want to retest. |
Hey sorry, I got distracted with work! :) Works a charm for me now just following the basic instructions in the readme. Thanks for fixing this! |
I can't get this module to install rabbitmq at all. The error I see is:
I'm using puppet with Vagrant.
Vagrantfile:
manifests/site.pp:
I installed the module with
puppet module install -i modules/ puppetlabs/rabbitmq
, so the only things inmodules/
areapt/
,stdlib/
, andrabbitmq
, none of which I've touched.Any help would be appreciated! Below is the complete output from
vagrant up
which triggers apuppet apply
.The text was updated successfully, but these errors were encountered: