this will be migrated to Jira by applying a label

https://www.puppet.com/docs/pe/2023.6/supported_operating_systems#supported_operating_systems has some kind of extensive package requirements for various operating systems. However, these lists have not been vetted against different OS versions (for example RHEL 7, 8 and 9) to determine if they are still valid. I noticed while testing against EL8 and EL9 systems some of these packages no longer exist and therefore aren't requirements. These lists should be cleaned up and presented as a table for each OS, something like:

Package|. EL7. | EL8 | EL9 |
|Primary|All Nodes|Primary|All Nodes|Primary|All Nodes|
pkgfor7 |. X. |. X. |. |. |. |. |
pkgfor78|. X. | X. | X. |. X. | | |
pkg7-9. |. X | X | X | X | X | X |

Describe the Change You Would Like

In puppetlabs/puppetserver@28fbc56 the default value for automatic certificate renewal got changed. The changelog doesn't list this: https://www.puppet.com/docs/puppet/8/server/release_notes#puppet-server-820

Also the whole autorenew configuration is not documented at https://www.puppet.com/docs/puppet/8/server/config_file_puppetserver

Describe the Bug

Hi, https://www.puppet.com/docs/pe/2021.5/release_notes_pe.html has no information when the PE releases actually happened.

Expected Behavior

I expect a release date in release notes.

Describe the Bug

https://www.puppet.com/docs/puppet/8/primary_agent_compatibility says agent 7 works only on puppetserver 7 and agent 8 only on puppetserver 8. I did some internal testing for PE customers and Agent 7 and 8 worked without issues on puppetserver 6/7/8. Can you please update the table or list which components aren't compatible?

Expected Behavior

a compatibility matrix that tells me why something isn't compatible.

Steps to Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'

Environment

• Version [e.g. 1.27.0]
• Platform [e.g. Ubuntu 18.04]

Additional Context

Add any other context about the problem here.

Describe the Change You Would Like

I would like the text or diagram to be changed so that they match up on page. Illustrated in the attachment.
https://www.puppet.com/docs/puppet/7/the_roles_and_profiles_method.html#configuring_roles_and_profiles

https://www.puppet.com/docs/pe/2023.6/hardware_requirements#hardware_requirements gives EC2 instance suggestions for large and XL environments. The EC2 suggestions appear to be out of date (they reference 5 series processors when 6 series processors are available with better price/performance), so wondering if we really should have those in the standard documentation to begin with. Would it maybe be better to move instance suggestions to the AWS reference architecture in "Patterns and Tactics"?

Please update the supported agent platforms for puppet 7 and 8

Puppet 7

https://www.puppet.com/docs/puppet/7/system_requirements#supported_operating_systems-packaged-platforms

Add

• Debian 12 (x86_64)
• Debian 12 (ARM)
• Red Hat Enterprise Linux 6 (i386)
• Red Hat Enterprise Linux 6 (x86_64)
• Red Hat Enterprise Linux 7 (x86_64)
• Red Hat Enterprise Linux 8 (x86_64)
• Red Hat Enterprise Linux 8 (ppc64le)

Modify

• Red Hat Enterprise Linux 9 (x86_64) currently it just says 9 without an architecture

Remove

• Ubuntu 24.04 (x86_64) (This won't be available until July)
• Red Hat Enterprise Linux 9 FIPS (that is PE only)

Puppet 8

https://www.puppet.com/docs/puppet/8/system_requirements#supported_operating_systems-packaged-platforms

Add

• Red Hat Enterprise Linux 7 (x86_64)
• Red Hat Enterprise Linux 8 (x86_64)
• Red Hat Enterprise Linux 8 (ppc64le)

Modify

• Debian 12 aarch64 and ARM different names for the same architecture. I think Debian prefers the aarch64 naming convention
• macOS 14 x86_64 and Intel are different names for the same architecture. Please drop the Intel variation.
• Red Hat Enterprise Linux 9 (x86_64) currently it just says 9 without an architecture
• Ubuntu 20.04 AARCH and 22.04 ARM64 should be aarch64

Remove

• Ubuntu 24.04 (x86_64) (This won't be available until July)
• Red Hat Enterprise Linux 9 FIPS (that is PE only)

In the OSP docs, there are multiple references to adding things to your Puppetfile and other code management tasks. However, code management and Puppetfiles are only defined and documented in the PE docs: https://www.puppet.com/docs/pe/2023.6/managing_puppet_code

This documentation (perhaps minus the Code Manager section) should probably be migrated to the OSP documentation.

One of the examples in https://www.puppet.com/docs/puppet/8/fact_overview.html#writing_facts_simple_resolutions-examples refers to osfamily, a legacy fact. The sample code should be changed from

Facter.add(:rubypath) do
  setcode 'which ruby'
end

Facter.add(:rubypath) do
  confine osfamily: "Windows"
  # Windows uses 'where' instead of 'which'
  setcode 'where ruby'
end

to something like

Facter.add(:rubypath) do
  setcode 'which ruby'
end

Facter.add(:rubypath) do
  confine 'os' do |os_fact|
    os_fact['family'] == "Windows"
  end
  # Windows uses 'where' instead of 'which'
  setcode 'where ruby'
end

https://www.puppet.com/docs/pe/2023.6/install-pe-using-installer-tarball

Section 1 (Verify the installation package) starts with "These steps are only required if your organization requires you to verify authenticity before installing packages." However, the very first step is to download the installation package (the tar file from the PE download site). Either this section should be retitled "Obtain and verify the installation package" and the first sentence should be moved to the verification steps, or there should be two sections - "Obtain the installation package" and "Verify the installation package". If this is done, the duplicated instructions under "Install from tarball" can be removed to reduce confusion.

The wget and curl examples should state that quotes are required if using the puppet.com download.cgi links.

In the "Install from tarball" section, the tar command needs to have -z included for installation packages downloaded from the puppet.com download.cgi links, since the files are stored in gzip format.

Meier
11:15 AM
The links on this page https://www.puppet.com/docs/puppet/8/plugins_in_modules#adding-plug-ins-to-a-module all point to ancient doc versions

Describe the Change You Would Like

From https://www.puppet.com/docs/puppet/7/config_file_oid_map :

Run puppetserver ca print to see changes made in custom_trusted_oid_mapping.yaml immediately without a restart.

But puppetserver ca print isn't a valid command.

Describe the Bug

https://www.puppet.com/docs/puppet/7/server/release_notes.html doesn't list changes for 7.15.0, 7.14.0 & 7.12.0

Expected Behavior

I expect a detailed changelog, if possible with linked github/public jira tickets. Instead 7.15.0 is missing completely, and 7.14.0/7.12.0 have no information at all.

Steps to Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'

Environment

• Version [e.g. 1.27.0]
• Platform [e.g. Ubuntu 18.04]

Additional Context

Add any other context about the problem here.

In PuppetDB setup for Postgresql, the database, 'puppetdb' doesn't yet exist when issuing the command:

psql puppetdb -c 'grant puppetdb_read to puppetdb'

The createdb command should precede the psql command:

sudo -u postgres sh
createuser -DRSP puppetdb
createuser -DRSP puppetdb_read
# For coordinating partition cleanup
psql puppetdb -c 'grant puppetdb_read to puppetdb'

createdb -E UTF8 -O postgres puppetdb
psql puppetdb -c 'revoke create on schema public from public'
psql puppetdb -c 'grant create on schema public to puppetdb'
psql puppetdb -c 'alter default privileges for user puppetdb in schema public grant select on tables to puppetdb_read'
psql puppetdb -c 'alter default privileges for user puppetdb in schema public grant usage on sequences to puppetdb_read'
psql puppetdb -c 'alter default privileges for user puppetdb in schema public grant execute on functions to puppetdb_read'

The documentation states that include_legacy_facts defaults to true on puppet 8:

https://www.puppet.com/docs/puppet/8/configuration.html#include-legacy-facts

This was true on puppet 7, but on puppet 8 the default is false.

Describe the Bug

The output of https://www.puppet.com/docs/puppet/7/hiera_merging#interpolation_functions-literal-function is wrong, literal won't add { nor }.

Specifically, it's this sentence:

The value of server_name_string would be %{SERVER_NAME}

The docs should say %SERVER_NAME without the braces.

Expected Behavior

Steps to Reproduce

hiera:

server_name_string: "%{literal('%SERVER_NAME')}"

Puppet:

echo { 'server_name_string:':
  message  => lookup('server_name_string'),
  withpath => false,
}

Outut:

# puppet agent -t --noop
Info: Refreshing CA certificate
Info: CA certificate is unmodified, using existing CA certificate
Info: Refreshing CRL
Info: CRL is unmodified, using existing CRL
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Notice: Catalog compiled by puppet.local
Notice: %SERVER_NAME

Environment

root@puppet ~ # dpkg -l | grep puppet
ii  puppet-agent                           8.4.0-1focal                      amd64        The Puppet Agent package contains all of the elements needed to run puppet, including ruby and facter.
ii  puppet-agent-oauth                     0.5.5-1                           all          OAuth Core Ruby implementation for Puppet Agent
ii  puppet8-release                        1.0.0-3focal                      all          Release packages for the Puppet 8 repository
ii  puppetdb                               8.4.1-1focal                      all          Puppet Labs puppetdb
ii  puppetdb-termini                       8.4.1-1focal                      all          Termini for puppetdb
ii  puppetserver                           8.4.0-1focal                      all          Puppet Labs puppetserver
ii  ruby-foreman-puppet                    5.1.2-1                           all          Foreman Puppet Plugin
ii  ruby-puppetdb-foreman                  6.0.2-1                           all          Foreman Puppetdb Plugin
root@puppet ~ #

Additional Context

Add any other context about the problem here.

The puppet 8 changelog has some incorrect links. For example here:
https://www.puppet.com/docs/puppet/8/release_notes_puppet#enhancements_puppet_x-8-3-0-PUP-11429
...the jira link is:
https://perforce.atlassian.net/browse/PUP-11429
...but should be:
https://puppet.atlassian.net/browse/PUP-11429

More recent entries have no links at all for jira issue numbers. For example here:
https://www.puppet.com/docs/puppet/8/release_notes_puppet#resolved_issues_puppet_x-8-5-1-PUP-11985

Thanks,
Corey

(https://www.puppet.com/docs/puppet/8/roles_and_profiles_example.html) links to the puppet 7 documentation for facts. The URL near the bottom of the page should be updated to point to puppet 8 documentation.

I think Java requirements documentation needs to be updated. On "Installing Puppet Server" for 7.29.1, it says that Java 8 is still supported.

https://www.puppet.com/docs/puppet/7/server/install_from_packages

On an Amazon Linux 2 server with Java 8 (java-1.8.0-openjdk-headless.x86_64 / 1:1.8.0.402.b06-1.amzn2.0.1):

After I upgraded puppetserver from 7.14 to 7.16 and puppetdb from 7.15 to 7.17, puppetdb kept crashing:

Requesting shutdown: java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer

It seems that Puppet is recently taking advantage of something not present in Java 8 (some method existed at compile time but is not present for the runtime).

Upgrading the server to Java 17 resolved the issue (java-17-amazon-corretto-headless.x86_64).