Upcoming changes to the rolling 'puppet' repos!

[Morgan Rhodes]

Hi all!

Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet' repos to point to the new 'puppet7' release from a couple of weeks ago. If you're already using the 'puppet' release packages (such as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm), your repos will start pointing to puppet7 tomorrow.

Let us know if you run into any issues!

Thanks,

Morgan

--

Morgan Rhodes

Release Engineering

mor...@puppet.com

she/her/hers

[Peter Meier]

Hi All,

> Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet'
> repos to point to the new 'puppet7' release from a couple of weeks ago.
> If you're already using the 'puppet' release packages (such
> as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm

> <http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm>), your repos

> will start pointing to puppet7 tomorrow.

Anybody having VMs / Baremetals / ... using VLANs: You will run into a
regression with Facter 4 that will stop puppet 7 from working on these
machines:

https://tickets.puppetlabs.com/browse/FACT-2870

The fix is there, but there is no release yet containing the fix. So
it's worth holding these machines of from being updated on the rolling
repos.

Additionally, there are a couple of regressions regarding how networking
facts are being reported by Facter 4:

https://tickets.puppetlabs.com/browse/FACT-2871
https://tickets.puppetlabs.com/browse/FACT-2872

If you are depending on these facts in your manifests (e.g. in a
condition), it might be the case that puppet will do something
differently. I suggest checking your manifests for the usage of these facts.

I didn't check the bug tracker thoroughly for other regressions, but I
have seen a few more. So it might worth looking into it, as regressions
in fact reporting can have unintended side-effects.

And really only cosmetic wise, you get a bunch of warnings in puppet 7
for the user and exec types:

https://tickets.puppetlabs.com/browse/MODULES-10876
https://tickets.puppetlabs.com/browse/PUP-10790

They are not really an issue, but might affect you if you are parsing
the output. E.g. filtering cron output -> cron emails are sent out with
these alerts.

Other than that: Puppet 7 runs smoothly, be sure to re-install your
gems, as it switches to Ruby 2.7

best

~pete

[Josh Cooper]

Thanks Pete for putting this together! Some comments below:

On Wed, Dec 2, 2020 at 12:33 AM Peter Meier <peter...@immerda.ch> wrote:

Hi All,

> Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet'
> repos to point to the new 'puppet7' release from a couple of weeks ago.
> If you're already using the 'puppet' release packages (such
> as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm
> <http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm>), your repos
> will start pointing to puppet7 tomorrow.


Anybody having VMs / Baremetals / ... using VLANs: You will run into a
regression with Facter 4 that will stop puppet 7 from working on these
machines:

https://tickets.puppetlabs.com/browse/FACT-2870

The fix is there, but there is no release yet containing the fix. So
it's worth holding these machines of from being updated on the rolling
repos.

All resolved issues should be available in nightly puppet7 builds, such as http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm. It'd be great to get confirmation in the next few days that these issues are in fact fixed.

Also all puppet6 builds include facter4 as an opt-in feature, so you can try it out before upgrading to puppet7:

# puppet --version
6.19.1

# puppet facts find | grep facter
    "facterversion": "3.14.14",
# puppet config set facterng true --section main
# puppet facts find | grep facter
    "facterversion": "4.0.43",

 

Additionally, there are a couple of regressions regarding how networking
facts are being reported by Facter 4:

https://tickets.puppetlabs.com/browse/FACT-2871
https://tickets.puppetlabs.com/browse/FACT-2872

If you are depending on these facts in your manifests (e.g. in a
condition), it might be the case that puppet will do something
differently. I suggest checking your manifests for the usage of these facts.

I didn't check the bug tracker thoroughly for other regressions, but I
have seen a few more. So it might worth looking into it, as regressions
in fact reporting can have unintended side-effects.

We've started adding a 'platform_7.1' label to keep track of these, see https://tickets.puppetlabs.com/issues/?jql=labels%20%3D%20platform_7.1

And really only cosmetic wise, you get a bunch of warnings in puppet 7
for the user and exec types:

https://tickets.puppetlabs.com/browse/MODULES-10876
https://tickets.puppetlabs.com/browse/PUP-10790

They are not really an issue, but might affect you if you are parsing
the output. E.g. filtering cron output -> cron emails are sent out with
these alerts.

Other than that: Puppet 7 runs smoothly, be sure to re-install your
gems, as it switches to Ruby 2.7

best

~pete

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/354bd76b-c85c-3026-9906-b7c3d20adf3b%40immerda.ch.

Josh

--

Josh Cooper | Software Engineer

jo...@puppet.com

[Peter Meier]

Hi Josh,

> All resolved issues should be available in nightly puppet7 builds, such
> as http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm

> <http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm>.

> It'd be great to get confirmation in the next few days that these issues
> are in fact fixed.

Unfortunately, the EL 7 nightly repo wants to install el8 content, which
is a) wrong and b) is not found in the repo. See below.

So I installed the rpm directly:

yum update
http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet-agent-7.0.0.103.gf0655d02-1.el7.x86_64.rpm


Which worked and I confirmed in the ticket that this fixes the issue.

~pete

# grep puppet /etc/yum.repos.d/*
/etc/yum.repos.d/puppet7-nightly.repo:[puppet7-nightly]
/etc/yum.repos.d/puppet7-nightly.repo:baseurl=http://nightlies.puppet.com/yum/puppet7-nightly/el/7/$basearch
/etc/yum.repos.d/puppet7-nightly.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet7-nightly-release
/etc/yum.repos.d/puppet.repo:[puppet]
/etc/yum.repos.d/puppet.repo:baseurl=https://yum.puppetlabs.com/puppet/el/7/$basearch
/etc/yum.repos.d/puppet.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet-release
/etc/yum.repos.d/puppet.repo:[puppet-source]
/etc/yum.repos.d/puppet.repo:baseurl=https://yum.puppetlabs.com/puppet/el/7/SRPMS
/etc/yum.repos.d/puppet.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet-release

# rpm -qf /etc/yum.repos.d/puppet7-nightly.repo
puppet7-nightly-release-1.0.0-2.el7.noarch

# yum update --disablerepo=puppet
Loaded plugins: fastestmirror, priorities
Repository base is listed more than once in the configuration
Repository centosplus is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository updates is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: mirror.imt-systems.com
* centos7-plus: centos.bio.lmu.de
* epel: mirrors.ircam.fr
* extras: linuxsoft.cern.ch
* nux-dextop: mirror.li.nux.ro
* updates: mirror.imt-systems.com
939 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package puppet-agent.x86_64 0:7.0.0-1.el7 will be updated
---> Package puppet-agent.x86_64 0:7.0.0.103.gf0655d02-1.el8 will be an
update
---> Package puppet7-nightly-release.noarch 0:1.0.0-2.el7 will be updated
---> Package puppet7-nightly-release.noarch 0:1.0.0-2.el8 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================
Package Arch Version
Repository Size
========================================================================================================================================
Updating:
puppet-agent x86_64
7.0.0.103.gf0655d02-1.el8 puppet7-nightly 24 M
puppet7-nightly-release noarch 1.0.0-2.el8
puppet7-nightly 14 k

Transaction Summary
========================================================================================================================================
Upgrade 2 Packages

Total download size: 25 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for puppet7-nightly
puppet7-nightly-release-1.0.0- FAILED

http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet7-nightly-release-1.0.0-2.el8.noarch.rpm:
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use
https://bugs.centos.org/.

puppet-agent-7.0.0.103.gf0655d FAILED

http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet-agent-7.0.0.103.gf0655d02-1.el8.x86_64.rpm:
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.


Error downloading packages:
puppet7-nightly-release-1.0.0-2.el8.noarch: [Errno 256] No more
mirrors to try.
puppet-agent-7.0.0.103.gf0655d02-1.el8.x86_64: [Errno 256] No more
mirrors to try.