+1 on the migration in the course of this year. Earlier we begin, sooner we'll be done ;) -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Wed, Apr 19, 2017 at 4:53 PM, Roman Shaposhnik <[email protected]> wrote: > Speaking of which, IIRC Puppet 3 is officially EOL starting 2017. > > Should we collectively invest effort in making sure that Bigtop 1.3 > is running 100% on Puppet 4? > > Do folks know of any issues that would prevent this migration? > > Thanks, > Roman. > > On Wed, Apr 19, 2017 at 11:14 AM, Kevin Monroe > <[email protected]> wrote: >> Heads up to those using the "apt" module from puppetlabs. Today, apt-3.0.0 >> was released: >> >> https://forge.puppet.com/puppetlabs/apt/changelog >> >> From the changelog: >> >> "If you're still running Puppet 3, remain on the latest puppetlabs-apt 2.x >> release for now, and see the documentation to upgrade to Puppet 4." >> >> If you attempt to use apt 3.0.0, puppet apply will fail like this: >> >> Error: Evaluation Error: Error while evaluating a Function Call, Must pass >> update_defaults to Class[Apt] at >> /home/ubuntu/bigtop.release/bigtop-1.2.0/bigtop-deploy/puppet/manifests/site.pp:50:8 >> on node juju-8d1ef7-12.lxd >> >> Install the latest 2.x module like this: >> >> $ sudo puppet module install puppetlabs-apt --version 2.4.0 >> >> Thanks, >> -Kevin
