Issue #19982 has been updated by Reid Vandewiele.
This still seems like a bug to me. Is this an Error, Warning, or Info message in the logs? I can see this making sense as an Info message but if it's really coming through the logs as an Error or a Warning, then I would say that's a bug. Setting ca=false is not an erroneous configuration, nor is it one that should be raising a warning. Sure, it should be noted, but that's more an Info than a Warn. In *any* multi-master configuration the most typical setting for master systems will be ca=false, and so we should not be getting errors or warnings about that correct and legitimate configuration every time the Master service starts. I wasn't able to find after a quick grep exactly where in the codebase this message is being generated. Can someone confirm and report on what error level this message is coming through as, or if there are other conditions besides setting ca=false that result in this error being displayed? Aside: a quick Google for answers as to when to use each warning level (Info, Warn, Error, etc) produced [this link](http://stackoverflow.com/questions/2031163/when-to-use-log-level-warn-vs-error) as a decent answer, though by no means authoritative. ---------------------------------------- Bug #19982: "This master is not a CA" error message is unhelpful https://projects.puppetlabs.com/issues/19982#change-94958 * Author: William Van Hevelingen * Status: Needs More Information * Priority: Normal * Assignee: William Van Hevelingen * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- <pre> Mar 29 02:53:50 tassadar tassadar puppet-master[11623]: this master is not a CA </pre> Our logs are full of the above error. Our CA server is zeratul (puppetca is a cname for it) and our puppetmaster (tassadar) is has CA set to false and has ca_server set to puppetca.cat.pdx.edu. All of the clients have ca_server set to puppetca.cat.pdx.edu as well. So I'm confused why we are getting the error in the first place. We're using pupppet version 3.1.1 and I think the error was present in the 2.7.x series as well. <pre> root@tassadar:~# cat /etc/puppet/puppet.conf [main] modulepath=/etc/puppet/environments/$environment/modules/internal:/etc/puppet/environments/$environment/modules/public manifest=/etc/puppet/environments/$environment/manifests/site.pp logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=true runinterval=1380 configtimeout=600 splay=true report=true ca_server = puppetca.cat.pdx.edu server=tassadar.cat.pdx.edu [master] ca = false storeconfigs = true storeconfigs_backend = puppetdb reports = http reporturl = http://stromboli.cat.pdx.edu:3000/reports/upload reportdir = /disk/trump/puppet-reports [user] environment = production </pre> -- 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.
