Puppet Platform 6.27.0 is now available!

22 views
Skip to first unread message

Puppet Product Updates

unread,
Apr 19, 2022, 6:50:23 PMApr 19
to puppet-...@googlegroups.com, Puppet Developers, Puppet Users

The release contains new features, minor enhancements, and bug fixes including:

 

Agent 6.27.1

  • Adds macOS 12 (x86_64) as a supported Agent platform

  • Allows use of puppet certificate for client HTTPS authentication with external CAs

 

PuppetDB 6.21.0

  • Ubuntu 20.04 and SUSE Linux Enterprise 15 are now supported.

  • PuppetDB will no longer run a garbage collection on startup. This may substantially reduce the time required before PuppetDB begins accepting commands and queries.

  • PuppetDB should require much less time and memory when parsing some PQL queries

  • The fact path GC now runs no more than once every 24 hours by default. This should be much less expensive in most cases, in exchange for a potentially slower response to the disappearance of individual fact paths.

 

Server 6.19.0 

  • Adds SUSE Linux Enterprise 15 as supported Server platform

  • Server CA now supports using a type 2 key identifier

 

 

For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/6/release_notes_osp.html

Puppet Product Updates

unread,
Apr 19, 2022, 7:07:57 PMApr 19
to puppet-...@googlegroups.com, Puppet Developers, Puppet Users
Correction: An email sent earlier erroneously said that Puppet Platform 6.27.0 was released. This should have said Puppet Platform 6.27.1. Thanks for your understanding!

Steve Huston

unread,
Apr 21, 2022, 10:32:57 AMApr 21
to puppet...@googlegroups.com
I upgraded this morning, and found that the package is named
puppet-agent-6.27.1-1.el7.x86_64, however the program itself also
thinks it is 6.27.0 which confuses the puppet_agent module:

Apr 21 10:25:03 coathook puppet-agent[11565]: Starting Puppet client
version 6.27.0
Apr 21 10:26:54 coathook puppet-agent[11569]: Could not update:
Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0'
returned 1: Error: Nothing to do
Apr 21 10:26:54 coathook puppet-agent[11569]:
(/Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure)
change from '6.27.1-1.el7' to '6.27.0' failed: Could not update:
Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0'
returned 1: Error: Nothing to do (corrective)
Apr 21 10:26:54 coathook puppet-agent[11569]:
(/Stage[main]/Puppet_agent::Install/Puppet_agent_end_run[6.27.0])
Dependency Package[puppet-agent] has failures: true
Apr 21 10:26:54 coathook puppet-agent[11569]:
(/Stage[main]/Puppet_agent::Install/Puppet_agent_end_run[6.27.0])
Skipping because of failed dependencies


On Tue, Apr 19, 2022 at 7:07 PM Puppet Product Updates
<puppet-prod...@puppet.com> wrote:
>
> Correction: An email sent earlier erroneously said that Puppet Platform 6.27.0 was released. This should have said Puppet Platform 6.27.1. Thanks for your understanding!
>
> On Tue, Apr 19, 2022 at 3:49 PM Puppet Product Updates <puppet-prod...@puppet.com> wrote:
>>
>> The release contains new features, minor enhancements, and bug fixes including:
>>
>>
>>
>> Agent 6.27.1
>>
>> Adds macOS 12 (x86_64) as a supported Agent platform
>>
>> Allows use of puppet certificate for client HTTPS authentication with external CAs
>>
>>
>>
>> PuppetDB 6.21.0
>>
>> Ubuntu 20.04 and SUSE Linux Enterprise 15 are now supported.
>>
>> PuppetDB will no longer run a garbage collection on startup. This may substantially reduce the time required before PuppetDB begins accepting commands and queries.
>>
>> PuppetDB should require much less time and memory when parsing some PQL queries
>>
>> The fact path GC now runs no more than once every 24 hours by default. This should be much less expensive in most cases, in exchange for a potentially slower response to the disappearance of individual fact paths.
>>
>>
>>
>> Server 6.19.0
>>
>> Adds SUSE Linux Enterprise 15 as supported Server platform
>>
>> Server CA now supports using a type 2 key identifier
>>
>>
>>
>>
>>
>> For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/6/release_notes_osp.html
>
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAFH7jMW2%3DMTFtgAAJGzqisvOrBXdX_qUac6%2BRCWba30ODRuRfA%40mail.gmail.com.



--
Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci
Princeton University | ICBM Address: 40.346344 -74.652242
345 Lewis Library |"On my ship, the Rocinante, wheeling through
Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus,
(267) 793-0852 | headlong into mystery." -Rush, 'Cygnus X-1'

Josh Cooper

unread,
Apr 21, 2022, 12:20:20 PMApr 21
to puppet...@googlegroups.com
On Thu, Apr 21, 2022 at 7:32 AM Steve Huston <hus...@astro.princeton.edu> wrote:
I upgraded this morning, and found that the package is named
puppet-agent-6.27.1-1.el7.x86_64, however the program itself also
thinks it is 6.27.0 which confuses the puppet_agent module:

Apr 21 10:25:03 coathook puppet-agent[11565]: Starting Puppet client
version 6.27.0
Apr 21 10:26:54 coathook puppet-agent[11569]: Could not update:
Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0'
returned 1: Error: Nothing to do
Apr 21 10:26:54 coathook puppet-agent[11569]:
(/Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure)
change from '6.27.1-1.el7' to '6.27.0' failed: Could not update:
Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0'
returned 1: Error: Nothing to do (corrective)
Apr 21 10:26:54 coathook puppet-agent[11569]:
(/Stage[main]/Puppet_agent::Install/Puppet_agent_end_run[6.27.0])
Dependency Package[puppet-agent] has failures: true
Apr 21 10:26:54 coathook puppet-agent[11569]:
(/Stage[main]/Puppet_agent::Install/Puppet_agent_end_run[6.27.0])
Skipping because of failed dependencies



This is a bug in the puppet_agent module when using the "auto" parameter, see https://tickets.puppetlabs.com/browse/MODULES-11315 You can workaround the issue by specifying the desired version explicitly. The module assumes the version of the puppet library the compiler is using (derived from Puppet::PUPPETVERSION) is the same as the version of the puppet-agent package. The versions are usually updated together, but it is not always true, as sometimes we update ruby/openssl/curl in the puppet-agent package due to CVEs without making changes to the puppet library.

Steve Huston

unread,
Apr 27, 2022, 9:07:12 AMApr 27
to puppet...@googlegroups.com
On Thu, Apr 21, 2022 at 12:20 PM Josh Cooper <jo...@puppet.com> wrote:
> On Thu, Apr 21, 2022 at 7:32 AM Steve Huston <hus...@astro.princeton.edu> wrote:
>> Apr 21 10:25:03 coathook puppet-agent[11565]: Starting Puppet client
>> version 6.27.0
>> Apr 21 10:26:54 coathook puppet-agent[11569]:
>> (/Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure)
>> change from '6.27.1-1.el7' to '6.27.0' failed: Could not update:
>> Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0'
>> returned 1: Error: Nothing to do (corrective)
> This is a bug in the puppet_agent module when using the "auto" parameter, see https://tickets.puppetlabs.com/browse/MODULES-11315 You can workaround the issue by specifying the desired version explicitly. The module assumes the version of the puppet library the compiler is using (derived from Puppet::PUPPETVERSION) is the same as the version of the puppet-agent package. The versions are usually updated together, but it is not always true, as sometimes we update ruby/openssl/curl in the puppet-agent package due to CVEs without making changes to the puppet library.

But what would I force it to? 6.27.1-1 isn't what the package reports
internally, so if I force that it'll find it via yum but then complain
on every run that the installed version is older than it should be,
then fail when the yum upgrade says it's already installed. 6.27.0
doesn't exist, so if I manually install 6.27.1-1 everywhere it will
complain that the installed version is newer than the forced one and
it can't find the old one to downgrade to. So far I've just kept it
at 6.26.0 until they reach parity, I don't see any other way to
continue to use the puppet_agent module and do otherwise.

Based on the comments on the bug now that weren't there last week, I'm
guessing I'm not alone in this confusion, and staying at 6.26.0 until
the assumed 6.27.2 comes out is probably for the best.

Michael Hashizume

unread,
Apr 27, 2022, 7:46:40 PMApr 27
to puppet...@googlegroups.com
Sorry for the confusion on this one. In future releases we'll ensure that the puppet-agent and puppet versions match, even in edge cases like the one we encountered in this release.

If I understand your issue Steve, you should be able to specify the package_version parameter to 6.27.1 with the puppet-agent module to upgrade your agent:

[root@immodest-roll ~]# rpm -qa | grep puppet-agent
puppet-agent-6.26.0-1.el7.x86_64
[root@immodest-roll ~]# cat manifest.pp
class {'::puppet_agent':
  package_version => '6.27.1',
}
[root@immodest-roll ~]# /opt/puppetlabs/bin/puppet apply manifest.pp
Notice: Compiled catalog for immodest-roll.delivery.puppetlabs.net in environment production in 0.23 seconds
Notice: /Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure: ensure changed '6.26.0-1.el7' to '6.27.1'
Notice: Stopping run after puppet-agent upgrade. Run puppet agent -t or apply your manifest again to finish the transaction.
Notice: Applied catalog in 12.51 seconds
[root@immodest-roll ~]# rpm -qa | grep puppet-agent
puppet-agent-6.27.1-1.el7.x86_64

Michael Hashizume
Software Engineer, Puppet Agent


--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages