What's the best way to test upgrades of puppetmaster? I'm trying to migrate from 3.x to 4.x on a small network. An obvious step for me was to create the new manifests on a new VM and then to confirm that the existing puppet agents wouldn't have any changes if they try to use that server for updates.
However, this approach falls as the certificates on the clients aren't recognised by the server. I'd guess that there's going to be similar identity issues from the clients' point of view if I get past this step. Is there a more pragmatic test plan to follow? The puppet documentation seems to leave it as an exercise to the user that 'nothing has broken' in the migration. Clearly this makes sense for changes to the client configurations, but even then some sort of 'diff' between the configurations would help. tc -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKZLxiUcbkfcOZ7a0ciAAaK8WercHQZxY4Fv2G-21CsYG5xODg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
