-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
Debian installation on mco > 2.8 removes plugins path from libdir #326
Comments
Here is how mcollective-puppet-agent looks on Ubuntu 16.04
/usr/local/share/mcollective though is gone from mcollective-common
Not sure if you can simply switch core_libdir and site_libdir without affecting older versions, which is what I am testing our infrastructure (12.04, 14.04, 16.04). I can though say that the current configuration will not work on 16.04 unless you're possibly installing from the source packages or something as then the source would get copied to your libdir and all would be well. Does a clean libdir and a fresh install of mcollective-puppet-agent really work on your test server with mco > 2.8? |
And I think this issue is along the same lines:
This will install mcollective-puppet-agent and then the next run will filebucket it! As the package will be installed under the site plugins directory. |
As I've commented in issue #325 you should be using the Puppetlabs-provided MCollective packages on 12.04 and 14.04. If you then set class { '::mcollective':
...
core_libdir => '/usr/share/mcollective/plugins',
...
} That's what we currently do on 12.04 and 14.04, using this module and MCollective 2.9 (from the Puppetlabs packages). Unfortunately Puppetlabs do not provide MCollective packages on 16.04, so you can either try to make it work with whatever Ubuntu provides, or can you read through https://tickets.puppetlabs.com/browse/MCO-722 for other ideas. As you can see the whole situation is a mess and I am not impressed by how Puppetlabs seem to treat MCollective more and more like a second-class citizen. Semi-related question: how do you get Puppet 3.8 to work on 16.04? The default Ruby version on 16.04 is 2.3 which Puppet 3.8 does not support. Do you install an older Ruby version, perhaps from the Brightbox PPAs? |
This works nicely. I did not catch the need to set core_libdir as a necessity for Ubuntu in the docs; maybe this should be updated in the README file? This is the output from a 16.04 LTS server we have.
|
I see, thank you. So you use the Puppet 3.8 packages provided by Ubuntu, not by Puppetlabs. I assume the Ubuntu package maintainers patched Puppet and its dependencies so that they work properly with Ruby 2.3.x. Which makes sense, since Puppetlabs don't even provide Puppet 3.8 packages for Ubuntu 16.04 any more (only PC1/AIO for Puppet 4). Good to know! |
Mcollective 1.11.1
Puppet 3.8
OS: Ubuntu 16.04
According to the docs, the way I understand them, the plugins directory needs to be retained. The core lib needs can be taken away after 2.8. The problem with the following code is that you remove the plugins directory and only retain the core lib directory.
libdir = /usr/local/share/mcollective
when it should be
libdir = /usr/share/mcollective/plugins
I think the code should be something like this.
The text was updated successfully, but these errors were encountered: