mcollectived LoadError (mcollective/registration/choria.rb)

[Gustavo]

Hi,

I'm followind Choria Deployment; I'm fine with the network broker and client, but when running puppet in nodes with "include mcollective" and "mcollective::server: true" set, mcollectived can't start:

Warning: Downgrading to PSON for future requests

Info: Using configured environment 'teamqueens'

Info: Retrieving pluginfacts

Info: Retrieving plugin

Info: Loading facts

error 2020/01/21 16:32:13: pluginmanager.rb:171:in `rescue in loadclass' Failed to load Mcollective::Registration::Choria: cannot load such file -- mcollective/registration/choria.rb

Info: Caching catalog for xxx

Info: Applying configuration version '1579642335'

Error: Systemd start for mcollective failed!

Jan 21 16:26:26 xxx systemd[1]: Starting The Marionette Collective...

Jan 21 16:26:26 xxx mcollectived[1240]: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/pluginmanager.rb:169:in `load': cannot load such file -- mcollective/registration/choria.rb (LoadError)

Jan 21 16:26:26 xxx mcollectived[1240]:         from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/pluginmanager.rb:169:in `loadclass'

Jan 21 16:26:26 xxx mcollectived[1240]:         from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/config.rb:167:in `loadconfig'

Jan 21 16:26:26 xxx mcollectived[1240]:         from /opt/puppetlabs/puppet/bin/mcollectived:57:in `<main>'

Jan 21 16:26:26 xxx systemd[1]: mcollective.service: Control process exited, code=exited status=1

Jan 21 16:26:26 xxx systemd[1]: mcollective.service: Failed with result 'exit-code'.

Jan 21 16:26:26 xxx systemd[1]: Failed to start The Marionette Collective.

#:/etc/puppetlabs/mcollective# cat server.cfg

classesfile = /opt/puppetlabs/puppet/cache/state/classes.txt

collectives = mcollective

connector = nats

daemonize = 1

factsource = yaml

identity = xxx

libdir = /opt/puppetlabs/mcollective/plugins

logfile = /var/log/puppetlabs/mcollective.log

main_collective = mcollective

plugin.rpcaudit.logfile = /var/log/puppetlabs/mcollective-audit.log

plugin.yaml = /etc/puppetlabs/mcollective/generated-facts.yaml

registerinterval = 10

registration = Choria

rpcaudit = 1

rpcauditprovider = choria

rpcauthorization = 1

rpcauthprovider = action_policy

securityprovider = choria

# dpkg -l puppet-agent

Desired=Unknown/Install/Remove/Purge/Hold

| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

||/ Name                                                  Version                         Architecture                    Description

+++-=====================================================-===============================-===============================-================================================================================================================

hi  puppet-agent                                          5.5.10-1bionic                  amd64                           The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mc

Any clue?

Thank you!

[R.I.Pienaar]

Hmm, suspect we've made some changes that is preventing the old ruby daemon from starting, its not really supported anymore.

We only support Puppet 6 and newer, this is a older Puppet.

You can try setting up Choria Server instead using https://choria.io/docs/configuration/choria_server/ but you might run into other Puppet 5 issues.

--

You received this message because you are subscribed to the Google Groups "Choria Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to choria-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/choria-users/03706262-d639-4ecc-bbbb-595b6de25abb%40googlegroups.com.

--

R.I.Pienaar / www.devco.net / @ripienaar

[Gustavo Randich]

thanks!

”but you might run into other Puppet 5 issues”

ok so puppet agent 6 is a requirement for choria server?

To view this discussion on the web visit https://groups.google.com/d/msgid/choria-users/8c493508-d0bb-47cf-bd1d-76ddd346591d%40www.fastmail.com.

[R.I. Pienaar]

Choria Server no, but the modules might have some 6 only assumptions, 6 is what we test on and the gem that replaces the puppet-agent delivered mcollective has recent changes you won’t have. 

You could run an older release that still support puppet 5 but really project wise we can’t support 5 anymore really. 

On 21 Jan 2020, at 23:37, Gustavo Randich <gustavo...@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/choria-users/CABUq5YUi%3D-z9f9MEeLp%3DdRnHNm7FDKVkYdOSm5pH%3DXa_xNk3%3DQ%40mail.gmail.com.

[Gustavo Randich]

I upgraded puppet agent and everything runs smoothly now

Thank you

To view this discussion on the web visit https://groups.google.com/d/msgid/choria-users/4C634528-C382-4F4E-8E24-D9738B18E9F7%40devco.net.

[John Gelnaw]

On Tuesday, January 21, 2020 at 5:52:42 PM UTC-5, R.I. Pienaar wrote:

Choria Server no, but the modules might have some 6 only assumptions, 6 is what we test on and the gem that replaces the puppet-agent delivered mcollective has recent changes you won’t have. 

You could run an older release that still support puppet 5 but really project wise we can’t support 5 anymore really. 

I'm somewhat grumpy having spent the last two days trying to track this problem down, so apologies if this comes out wrong....

But this product is increasingly frustrating.  

Puppet 5.x is, according to the documentation, supported until November 2020-- but you can't be bothered to support it any longer.

The Choria module (v. 0.15.0) on puppet forge claims to support Puppet 4.9.0 and greater, as does the mcollective_choria (v. 0.17.1) module-- but now I'm finding out that's apparently wrong.

You have yet to officially support Debian 10.x which has been out since July 2019-- and Debian isn't exactly an "obscure" distribution.

It's reaching a point where it's difficult to justify the software to my supervisor.

[Gustavo]

I have a line in my backlog that reads:

  "figure out how to gradually upgrade puppet agent from v5 to v6 agent on 10k machines without disrupting legacy mcolletive services (puppet agent 6 uninstalls mcollectived ruby daemon)"

I'm scared :)

[John Gelnaw]

On Friday, April 3, 2020 at 10:47:02 AM UTC-4, Gustavo wrote:

I have a line in my backlog that reads:

  "figure out how to gradually upgrade puppet agent from v5 to v6 agent on 10k machines without disrupting legacy mcolletive services (puppet agent 6 uninstalls mcollectived ruby daemon)"

I'm scared :)

FYI, rolling module "choria/mcollective_choria" back to version 0.16.1 solves the missing registration/choria.rb.  

Devs might want to flag version 0.17.x as incompatible with puppet 5.x.

[R.I.Pienaar]

On Fri, 3 Apr 2020, at 16:47, Gustavo wrote:

I have a line in my backlog that reads:

  "figure out how to gradually upgrade puppet agent from v5 to v6 agent on 10k machines without disrupting legacy mcolletive services (puppet agent 6 uninstalls mcollectived ruby daemon)"

I'm scared :)

Can I ask why not move to Choria? Puppet does not support mcollectived and the changes between Puppet 5 and 6 makes it a unreasonable burden to support both for me

[Gustavo]

I want to. But I need to do it *gradually*, with mcollectived/puppet 5 running along choria servers. I don’t want to couple the upgrade of puppet agents to version 6 just to test choria right now. When I tried to do that, I hit the error that started this thread.

[R.I.Pienaar]

OK, if you go to the versions mentioned earlier I think it will work. Assuming you have puppet 5 machines on the same master as 6 ones.

> --
> You received this message because you are subscribed to the Google
> Groups "Choria Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to choria-users...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/choria-users/d0f4e15f-c9f2-4033-bf00-5bfbcfdf23a2%40googlegroups.com.