Issue #7962 has been updated by Steven Lindberg.

Status changed from Accepted to In Topic Branch Pending Review
Target version changed from 2.7.x to 3.x
% Done changed from 0 to 100

Thanks Deepak, I took your advice and implemented the check when the agent 
communicates with the master. I attempted to limit the number of warnings as 
much a possible without having some kind of timeout, but it still might get a 
bit noisy. Maybe that's a good thing though :) More details in the pull 
request/commit messages:

https://github.com/puppetlabs/puppet/pull/1074

Note that I created a new branch since there were comments on some of the other 
commits, but I felt it was better to rebase them off of the up-to-date 3.x (and 
not have a jillion of them).
----------------------------------------
Feature #7962: Warn when a certificate approaches the expiration date
https://projects.puppetlabs.com/issues/7962#change-69966

Author: Jacob Helwig
Status: In Topic Branch Pending Review
Priority: High
Assignee: 
Category: logging
Target version: 3.x
Affected Puppet version: 
Keywords: 
Branch: 


It's especially troublesome if the CA or master certificate expires without any 
real warning.  We should be warning in the logs (possibly reports, too?) if any 
of the certificates (CA, master, agent) are approaching their expiration date.


-- 
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.

Reply via email to