Issue #9956 has been updated by Charlie Sharpsteen.
Redmine Issue [#9956](http://projects.puppetlabs.com/issues/9956) has been migrated to JIRA: <https://tickets.puppetlabs.com/browse/MCO-40> ---------------------------------------- Bug #9956: servers have dependency on collective "mcollective" which can be broken by config file change https://projects.puppetlabs.com/issues/9956#change-101399 * Author: Luke Bigum * Status: Accepted * Priority: Low * Assignee: * Category: Core * Target version: * Keywords: * Branch: * Affected mCollective version: ---------------------------------------- I'm using a number of collectives by specify the "collectives = foo,bar,baz" in the server.cfg file. When starting a 1.3.1 server, it complains that "mcollective" is not a valid collective, as I haven't explicitly added it. W, [2011-10-06T17:14:50.329529 #27270] WARN -- : base.rb:50:in `target_collective' Sending registration to mcollective: mcollective is not a valid collective E, [2011-10-06T17:14:50.331950 #27270] ERROR -- : base.rb:29:in `run' Sending registration message failed: Unknown collective 'mcollective' known collectives are 'all' Easy to work around, but a more robust approach might be to silently generate the "mcollective" collective if it's not there and it's needed so badly. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
