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

version parameter does not work #154

Closed
mattboston opened this issue Dec 14, 2013 · 4 comments
Closed

version parameter does not work #154

mattboston opened this issue Dec 14, 2013 · 4 comments

Comments

@mattboston
Copy link

When using version in the class definition is ignored and the version defined in the config.pp is the one used.

class { 'rabbitmq':
version => "3.2.2-1",
config_cluster => true,
cluster_nodes => [ "${rabbitmq_node1}", "${rabbitmq_node2}" ],
cluster_node_type => 'disc',
erlang_cookie => "${erlang_cookie}",
wipe_db_on_cookie_change => true,
}

@kraeuschen
Copy link

hi version is a little bit misleading, i guess its unused currently.

to install an fixed version use:

 class { '::rabbitmq':
    delete_guest_user   => true,
    package_ensure      => hiera('rabbit::version'),
...

@flozano
Copy link

flozano commented Feb 24, 2014

We've been hit by this. This workaround doesn't work in RHEL/CentOS.

@flozano
Copy link

flozano commented Mar 3, 2014

Any plan to fix this?

@wyardley
Copy link
Contributor

It is misleading, and I've actually taken it out in #493 (the module now just gets the version from status commands, though this could potentially cause some chicken / egg problems). I'm going to mark this as closed, I did try to add some docs mentioning the bit about using $package_ensure instead.

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

4 participants