Jira (PUP-3122) It's time we wrote a more usable no cert found warning!

[Nicholas Fagerlund (JIRA)]

Title: Message Title

Nicholas Fagerlund commented on an issue   Re: It's time we wrote a more usable no cert found warning! I suggest the following two messages. Waitforcert disabled: Couldn't fetch certificate from CA server; you may still need to sign this agent's certificate (#{CERTNAME}). Exiting now because the waitforcert setting is set to 0. Enabled: Couldn't fetch certificate from CA server; you may still need to sign this agent's certificate (#{CERTNAME}). Will try again in #{WAITFORCERT}. Add Comment   Puppet / PUP-3122 It's time we wrote a more usable no cert found warning! When you run the agent after it's submitted a CSR, but before the master has signed it, you get the warning {{no certificate found and waitforcert is disabled}}. This causes an incredible amount of consternation in the field because it sounds like "you done screwed up". Can we simply amend it to something like this? {{No certificate found and waitfo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.