Feature #11835

Upgrade Puppet master and clients to 3.8

Added by intrigeri 2016-09-24 04:44:09 . Updated 2016-10-02 13:27:12 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.7
Start date:
2016-09-24
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
270

Description

That’s one recommended step towards migrating to Puppet 4, e.g. so that agents can connect to a v4 puppetmaster: https://docs.puppet.com/puppet/4.5/reference/upgrade_major_pre.html#update-to-the-latest-puppet-server-11x-puppet-38x-and-puppetdb-23x.

Subtasks

Related issues

Blocks Tails - Feature #11836: Stop stringifying Puppet facts Resolved 2016-09-24
Blocks Tails - Feature #11833: Make our Puppet code compatible with the "future" parser Resolved 2016-09-24

History

#1 Updated by intrigeri 2016-09-24 04:44:32

#2 Updated by intrigeri 2016-09-24 04:46:57

  • blocked by deleted (Feature #11834: Migrate our infrastructure to Puppet 4)

#3 Updated by intrigeri 2016-09-24 04:47:02

#4 Updated by intrigeri 2016-09-24 04:48:37

#5 Updated by intrigeri 2016-09-24 04:50:24

#6 Updated by intrigeri 2016-09-24 04:50:41

  • blocks Feature #11833: Make our Puppet code compatible with the "future" parser added

#7 Updated by intrigeri 2016-09-24 04:51:47

  • Assignee set to intrigeri
  • Target version set to Tails_2.7

#8 Updated by intrigeri 2016-10-01 21:01:39

jessie-backports has 3.8.5-2~bpo8+1 (not too far from Jessie’s 3.7.2-4) so this seems to be doable.

#9 Updated by intrigeri 2016-10-02 13:27:12

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100
  • Deliverable for set to 270

Done on all systems.

#10 Updated by intrigeri 2016-10-02 13:27:50

  • blocked by deleted (Feature #11837: Upgrade Puppet master to Puppet 4)