Issue #3644 has been updated by Markus Roberts. Status changed from Accepted to Rejected
So after looking at the code and thinking in a bit more detail about the semantics of waitforcert and onetime, I've come to the conclusion that this is in fact correct behavior. The numeric option on --waitforcert is not the _maximum_ amount of time to wait for the cert, it's the polling interval. The waitforcert option says that (if a certificate is needed to do a catalog run) to wait until it's received, checking every n seconds, with no maximum time, and them do the run. And --onetime means do exactly one catalog run; it doesn't mean "do one catalog run, so long as it doesn't take too long." There's no implicit timeout there either. Combined, they mean "wait until a certificate, arrives, checking every n seconds, do a catalog run, then exit," which is what it's doing. ---------------------------------------- Bug #3644: --waitforcert does not play nicely with --onetime http://projects.puppetlabs.com/issues/3644 Author: Alan Barrett Status: Rejected Priority: Normal Assigned to: Markus Roberts Category: executables Target version: 0.25.5 Affected version: 0.25.4 Keywords: Branch: running "puppetd --onetime --test --waitforcert 1" does not wait one second for the certificate and then exit; it loops forever printing <pre> warning: peer certificate won't be verified in this SSL session notice: Did not receive certificate </pre> once per second. -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
