In my testing the puppetlabs PuppetDB 4.4 package for jessie works as-is on stretch as well. Since (according to puppetlabs docs) 4.4 is the latest version of PuppetDB still supporting puppet 4, and there is not yet a stable Debian PuppetDB 4.4 package, let's port the puppetlabs jessie package to stretch.
Let's also think about conflicts that may arise in the future if/when a proper Debian PuppetDB package becomes available.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| puppetdb: add puppetdb4 apt component when puppetdb_major_version == 4 | operations/puppet | production | +9 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • aborrero | T178717 Upgrade wmcs instances and masters to puppet 4.8 | |||
| Resolved | None | T177254 Upgrade to puppet 4 (4.8 or newer) | |||
| Resolved | jbond | T184561 Modernize Puppet Configuration Management (2017-18 Q3 Goal) | |||
| Resolved | herron | T177253 Upgrade PuppetDB to version 4.4 | |||
| Resolved | herron | T185502 Port puppetlabs PuppetDB 4.4 package to stretch | |||
| Resolved | MoritzMuehlenhoff | T187257 puppetdb4: systemd config review |
Packages have been built for stretch and working ok labs puppetdb testing instance. To be added to main apt repo at a later date.
Upon closer inspection the puppetdb-termini package needed some adjustments to cooperate with the debian puppet packages (on a puppetmaster)
Packages have been rebuilt with these changes.
I noticed while working on puppetmaster on stretch that we didn't have a git repo to host puppetdb source (packages), so I created operations/debs/puppetdb for this purpose, to be populated
Change 417054 had a related patch set uploaded (by Herron; owner: Herron):
[operations/puppet@production] puppetdb: add puppetdb4 apt component when puppetdb_major_version >= 4
Change 417054 merged by Herron:
[operations/puppet@production] puppetdb: add puppetdb4 apt component when puppetdb_major_version == 4