On Fri, 30 Jun 2017 at 07:47 R.I. Pienaar <r...@devco.net> wrote: > > On 30 Jun 2017, at 01:22, Eric Sorenson <e...@puppet.com> wrote: > > On Jun 28, 2017, at 9:28 AM, R.I.Pienaar <r...@devco.net> wrote: > > People upgrading should note the PuppetDB dependency is now postgres > postgresql96, this is not stated on the package dependency metadata so > upgrade works fine but puppetdb fails to start until you update > > > Hm, as I understand it there isn't a package-level dependency on > postgresql at all because you can install puppetdb and postgres on > different hosts. > > > That's a good point. Sounds legit :) > > > The version bump is mentioned in the puppetdb 5 docs but it's probably > worth bringing that into the overall platform release notes > https://docs.puppet.com/puppetdb/5.0/#postgresql-96 > > > Yeah - I think though since it's now like "5 Platform" probably some kind > of holistic upgrade guide is needed. > > I have never updated PostgreSQL for puppetdb so it took a while to figure > out all the incantations needed to do that and there is definitely an order > in which this has to be done between the various components. Get it wrong > and you're running stuff with puppet apply on the master since you broke it > like I did :P > > I am still unsure how to do this easily since puppetdb 5 requires > puppetserver 5 I can only think of nasty break ways to do that update. How > did others do it? You will always end up with a completely down > puppetserver and now using the puppet module to manage puppetdb etc will > require apply. > > Version 4.x of PuppetDB works with Postgres 9.6.x, so it should be possible to upgrade Postgres first and then do the rest of the upgrade.
According to documentation PuppetDB 5.x should be able to process commands from the PuppetDB 4.x terminus as well, so upgrading puppetdb before puppet server should work I guess. Or do you mean there is a package level dependency on puppetserver 5? I've always been running them on separate hosts, so a dependency on having them on the same host sounds annoying. > > > Eric Sorenson - e...@puppet.com <eric.soren...@puppet.com> > director of product, ecosystem and platform > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/81F9258B-89EF-464C-9B1C-FDC677DE800C%40puppet.com > <https://groups.google.com/d/msgid/puppet-dev/81F9258B-89EF-464C-9B1C-FDC677DE800C%40puppet.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/E7AB3172-D214-4F8A-A335-C6526D93A316%40devco.net > <https://groups.google.com/d/msgid/puppet-dev/E7AB3172-D214-4F8A-A335-C6526D93A316%40devco.net?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAAAzDLeR_0NX5SJXOxYQYcq2E--O8WcvKWGOC9%3DNdbFD5UtTzA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
