Resolved issues

This page describes resolved issues in the latest Puppet Enterprise (PE) release.

For more information about this release, see:

Tip: This PE release contains several components that have additional release notes. Refer to Related release notes for more information.

Resolved issues in PE 2017.2.3

Agent packages for AIX, Solaris, OSX, and Windows weren’t synched correctly to compile masters

Applying any of the pe_repo::platform::aix_* classes on a compile master that couldn’t reach resulted in a failure.

Nodes with no reports generated console errors on report retrieval

If you clicked a node’s report list, and the node didn’t have any reports stored in PuppetDB, the console returned an error that it couldn’t retrieve the report.

Web-based installation in browsers set to Japanese still displayed in English

If the browser was set to ja-JP, the web-based installer displayed text in English.

Catalog compilation failed with older versions of the Puppet inifile module

Using a Puppet inifile module earlier than version 1.1.0 conflicted with the PE inifile module, resulting in catalog compilation failures.

Resolved issues in PE 2017.2.2

Compile masters couldn’t retrieve certain agent packages

Enterprise Linux and Ubuntu agent packages weren’t distributed to compile masters as expected through the pe_repo class.

Custom environments for preconfigured node groups were re-set on upgrade

If you changed the environments of preconfigured node groups, upgrading re-set the environments to production.

Orchestrator did not report correct job status if compile master restarted

If a compile master was restarted during an orchestrator job, the job statuses for agent nodes reporting to the compile master were all reported as “In progress.” The orchestrator now reports jobs status correctly if a compile master is restarted.

Console stops responding when navigating new group in separate window

In some cases, the PE console would stop responding if you tried to navigate a newly created node group in a separate tab or window while the group was still open in the original tab or window.

Incorrect response on /orchestrator/v1/inventory endpoint

POST requests to the /orchestrator/v1/inventory endpoint without a body/payload erroneously returned a 200 response. An invalid body for POST now correctly returns a 400 response.

Resolved issues in PE 2017.2

PE installed newer puppet-agent package

Previously, PE would install a newer puppet-agent package than expected if the Puppet Collection 1 (PC1) open source Puppet repos were set up on the system. In this release, the installer installs the specific version of the puppet-agent package that is expected.

Web-based installer didn’t support SLES 12 (SP1, SP2)

Previously, the web-based installer wasn’t supported on SLES 12 (SP1 or SP2), so you had to use the text-mode installation method. Web-based installation is now supported.

Upgrade failed if a PE Infrastructure node group name contained unexpected capitalization

Previously, installation failed if you changed the default capitalization for any PE Infrastructure node group names, because the installer was case insensitive. For example, if the installer encountered a PE Mcollective (lowercase “c”) node group when it expected a PE MCollective (uppercase “c”) node group, it returned an error about non-unique group names.

Installation failed on systems that used UTF-8 characters in file names

If you attempted to install Puppet Enterprise on a system that used UTF-8 characters in path or file names, installation failed with a message indicating errors in the pe.conf file.

Code Manager deploys timed out due to a script hanging indefinitely

In PE 2016.5 and 2017.1, Code Manager deploys hung and ultimately timed out for some users with a large number of native types in a single environment. This issue was caused by the generate-puppet-types.rb script hanging indefinitely during the pre-commit phase.

On Windows, puppet-code deploy failed for tokens with UTF-8 characters

On Windows systems, puppet-code deploy failed if you specified an authentication token that includes UTF-8 characters in the filename. This failure occurred only if you specified the token in the puppet-code.conf file or on the command line with the --token-file option.

Overview load time for deployments with a large number of facts

Previously, the Overview page in the PE console loaded very slowly for some deployments with a large number of facts. Page load time has been significantly decreased in this version.

Discard changes did not clear changes made to user roles

In PE 2016.5 and 2017.1, clicking Discard changes failed to clear pending user changes when altering user roles in the console.

Correct URL and page rendering when cancelling browser navigation

In previous versions of PE, using your browser’s back button would rewrite the URL to the previous page (if the previous page was in the console). If you cancelled this navigation, the URL would read incorrectly, and a refresh could potentially render the incorrect page. The URL will now render the correct page if you cancel the navigation. g

RBAC certificate whitelist didn’t reload when pe-console-services sent a HUP signal

Prior to this release, if pe-console-services was sent a HUP signal, the RBAC service would fail to reload the certificate whitelist, effectively caching the content at original startup. With this release, the certificate whitelist is reloaded when a HUP is received.

Node filtering not respected by pagination

In previous releases, if a filter was applied to the node list inventory, the filter was not carried over into subsequent pages.

CSV downloads in filtered views raised authentication errors

Previously, if you tried to download CSV tables from filtered views in the console, the console would raise an authentication error.

MCollective uses YAML.safe_load as default

The AES encryption and SSL security plugins now use YAML.safe_load to deserialize messages. This prevents potential attack vectors from deserializing YAML into classes. These plugins now require Ruby 2.1 or later to use YAML deserialization.

PuppetDB could not store sensitive parameters

This release corrects an issue in which adding the sensitive data type to the parameters of an existing resource caused catalog storage failures in PuppetDB.

PuppetDB filters null bytes in Resource Events fields

Previously, PuppetDB was unable to properly handle entries in the Windows registry that contained a default value of '\0'.

↑ Back to top