Issue #7982 has been updated by Brice Figureau.
Matthaus Litteken wrote: > So in commit 49d1e9da1381c77a3873965bad36ba6b33316882, the expire method got > removed from the cacher and the cacher was reworked (details in that commit > msg). It's not clear to me if this issue will still be present with the > changes from that commit, but as this patch uses the expire method, it can't > get merged as it stands. Yes the problem is that without this expire it can not work because the current ssl host is cached (see ssl/host.rb). If I don't have any ways to expire the current ssl host (which happens to be a singleton), then I'm screwed (except if I reintroduce selective expiration for ssl host). Anyway, I'll definitely check and fix the patch. ---------------------------------------- Bug #7982: puppet device fails on second device https://projects.puppetlabs.com/issues/7982 Author: Brice Figureau Status: Code Insufficient Priority: Normal Assignee: Category: network Target version: 2.7.4 Affected Puppet version: Keywords: Branch: https://github.com/masterzen/puppet/tree/tickets/2.7.x/7982 Puppet device fails when using more than one device because the SSL certs used for the second device is still the one of the first certificate. I believe I tested this when I implemented the feature :( -- 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.
