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

no means to remove mcollective from a node #363

Open
pvbiesen opened this issue Jan 29, 2018 · 0 comments
Open

no means to remove mcollective from a node #363

pvbiesen opened this issue Jan 29, 2018 · 0 comments

Comments

@pvbiesen
Copy link

pvbiesen commented Jan 29, 2018

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.10.9
  • Ruby: 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]
  • Distribution: Debian 9.3
  • Module version: 3.1.0

How to reproduce (e.g Puppet code you use)

Set server=>false and client=>false :

class{
'::mcollective':
manage_packages => false,
server => false,
client => false,

main_collective => 'mcollective',
collectives => 'mcollective',
server_loglevel => 'info',
connector => 'rabbitmq',
psk => 'XXXXXXXXXXXXX',
middleware_hosts => [ 'XXXXph.be','YYYYYYYph.be','ZZZZZZZZph.be'],
middleware_user => 'mcollective124',
middleware_password => XXXXXXXXXX',
rabbitmq_vhost => '/mcollective124', ;
}

What are you seeing

The module does not stop the server daemon and doesn't clean up the server.cfg and client.cfg .

What behaviour did you expect instead

The server daemon should be stopped and all alterations done previously by the module should be undone ( like removing the client.cfg and server.cfg ).

Output log

Any additional information you'd like to impart

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

1 participant