Hi Dan, I'm not upgrading, I'm installing a server from scratch. I want to upgrade just my puppetmaster and leave the clients alone for now, because Puppet is a huge part of our infrastructure I can't do it all in one pass.
I can get a single puppetmaster up and running. I cannot then get a second puppetmaster to be a client of the first puppetmaster. I also, at this point, can't roll back because SSL is totally screwed in my infrastructure now. So, I'm in fire-fighting mode. Thanks for your help, but I'm definitely done with this. --Paul On Tue, Nov 10, 2009 at 10:43 AM, Dan Bode <d...@reductivelabs.com> wrote: > Hi Paul, > > I am currently (but unfortunately slowly) staging this, so far I have done > the following: > > 1. installed .24.8 with passenger, tested > 2, Upgraded to .25.1(head from git) > 3. Reconfigured passenger > 4. Tested client/server on one machine > 5. Upgraded additional client machine to.25.1 > 6. Verified that client can get ssl keys and run puppetd against the server > > Can you get this far? Can you upgrade the CA server and connect client? > > My next step is to stage all of this with 2 puppetmasters using the methods > explained above. > > I will make a post once I get it working (its hard to find the time though, > this will take some effort). > > > regards, > > Dan > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
