Page MenuHomePhabricator

Match puppet version in Gemfile and actual box
Closed, ResolvedPublic

Description

The puppet version used by bundle is set as:

Gemfile~> 3.7.x
Gemfile.lock3.7.5

Debian Jessie came with 3.7.2 so we probably to stick to that, though that probably does not matter much ( upstream changelog is https://docs.puppet.com/puppet/3.7/release_notes.html#puppet-375 ).

The subject of this task is: what is the actual version of puppet running in the box? Maybe it is using 3.8.x which we had at some point or maybe it is even already on puppet 4?

The reason is to be able to run rspec puppet tests with the same version as on the box.

Event Timeline

hashar triaged this task as Normal priority.Dec 22 2017, 5:52 PM
hashar created this task.

On my stretch-migration testing VM:

$ vagrant ssh -- puppet --version
4.8.2
$ apt-cache show puppet
Package: puppet
Version: 4.8.2-5
Installed-Size: 5785
Maintainer: Puppet Package Maintainers <pkg-puppet-devel@lists.alioth.debian.org>
Architecture: all
Replaces: puppet-common (<< 4.5.1-1), puppetmaster-common (<< 4.4.2-1~)
Depends: init-system-helpers (>= 1.18~), adduser, facter, ruby-augeas, hiera, lsb-base, ruby | ruby-interpreter, ruby-deep-merge, ruby-rgen, ruby-safe-yaml, ruby-shadow
Recommends: debconf-utils, lsb-release, ruby-selinux
Suggests: ruby-rrd
Breaks: facter (<< 2.4.0~), puppet-agent (<< 4.8.1-3~), puppet-common (<< 4.5.1-1), puppetmaster-common (<< 4.4.2-1~)
Description: configuration management system
Description-md5: ef3dda3eed5993363eeb9d1652849320
Homepage: https://github.com/puppetlabs/puppet
Tag: admin::automation, admin::configuring, admin::file-distribution,
 admin::package-management, admin::user-management,
 implemented-in::ruby, interface::commandline, interface::daemon,
 network::client, role::program, works-with::file,
 works-with::software:package, works-with::software:running
Section: admin
Priority: optional
Filename: pool/main/p/puppet/puppet_4.8.2-5_all.deb
Size: 1122848
MD5sum: 63af0b28272b0ff8dc528bccf9a48412
SHA256: 6e00516561dc120e94697bab66cd55b63ec2e4f5fcf61e534b06ff8f6cc6b895

On a Jessie one, the initial provisioning is done with: 3.7.2

$ apt-cache policy puppet
puppet:
  Installed: 3.7.2-4+deb8u1
  Candidate: 4.8.2-5~bpo8+1
  Version table:
     4.8.2-5~bpo8+1 0
        100 https://mirrors.wikimedia.org/debian/ jessie-backports/main amd64 Packages
       1001 https://apt.wikimedia.org/wikimedia/ jessie-wikimedia/main amd64 Packages
     3.8.5-2~bpo8+2 0
       1001 https://apt.wikimedia.org/wikimedia/ jessie-wikimedia/backports amd64 Packages
 *** 3.7.2-4+deb8u1 0
        500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages
        500 http://security.debian.org/ jessie/updates/main amd64 Packages
        100 /var/lib/dpkg/status

I am pretty sure production upgraded to 3.8.5 before heading to 4.8.

Stretch will be the master branch in ~2 weeks (T181353). I wouldn't waste much energy on things like this in master right now.

Definitely :] I guess we can keep this around as a reminder to bump the Puppet version in the Gemfile to match the one installed in Stretch.

hashar closed this task as Resolved.Dec 26 2017, 9:02 AM

Thanks Bryan. I did the rspec-puppet patch on the stretch-migration. The Gemfile has puppet 4.8.2 which match the Debian package.