Known issues index

(↓ expand all ↓) (↑ collapse all ↑) |

Puppet Enterprise 2017.2

Overview
- Welcome to PE
- PE architecture overview
- Component versions in recent PE releases
- Getting support
- PE version numbers
Release notes
- New features and enhancements
- Known issues
- Resolved issues
Puppet platform documentation
Quick start guides
- Quick start guide for *nix users
- Quick start guide for Windows users
- Essential configuration tasks
Managing Windows nodes
- Installing PE for a Windows environment
- Basic tasks and concepts in Windows
- Managing Windows configurations
- Installing and using Windows modules
- Troubleshooting Puppet on Windows
Installing
- System requirements
- What gets installed where?
- Downloading PE and installing overview
- Web-based installation: monolithic
- Text-mode installation
- Purchasing and installing the PE license key
- Installing agents
- Installing network device agents
- Installing compile masters
- Load balancing compile masters
- Installing ActiveMQ hubs and spokes
- Installing PE client tools
- Uninstalling PE
- Installing standalone PE-PostgreSQL
- PE and external PostgreSQL Setup
Upgrading
- Upgrading PE: monolithic
- Upgrading PE: split
- Upgrading PE agents: *nix
- Upgrading PE agents: Windows
Migrating from 3.8
- Preparing for Migration to PE 2017.2
- Migrating from PE 3.8 to 2017.2: monolithic
- Migrating: important notes
- Major path changes
Configuring PE
- Your PE infrastructure
- Tuning Puppet Server
- Tuning the console
- Tuning PuppetDB
- Tuning orchestration
- Java arguments for PE
- Configuring ulimit for PE services
- Tuning mono installs (reference)
- Writing configuration files
- PE analytics data collection
- Static catalogs
Configuring high availability
- High availability overview
- Configure high availability
Monitoring infrastructure state
- Monitor current infrastructure state
- Explore your catalog with the node graph
- Analyze changes across Puppet runs
- View all packages in use
- Infrastructure reports
- Monitoring Puppet Server metrics
- Monitoring PE services
- Status API
Managing nodes
- Managing node requests
- Running Puppet on agent nodes
- Getting started with classification
- Grouping and classifying nodes
- Roles and profiles: Designing system configs
- Viewing node-specific information
- Making changes to node groups
- Removing nodes
- Preconfigured node groups
- How does inheritance work?
- Working with environments
- Node classifier service API
Managing access
- Accessing the console
- Role-based access control
- Connecting PE with external directory services
- About RBAC permissions
- Creating and managing users and user roles
- Token-based authentication
- Running agents without root privileges
- RBAC service API v1
- RBAC service API v2
  - Endpoints
  - Revoke tokens
- Activity service API
  - Endpoints
  - Activity reporting
Managing applications
- Application orchestration: Overview
- Application orchestration: Key concepts and workflow
Enforcing change with Puppet orchestrator
- Direct Puppet: a workflow
- Puppet orchestrator: overview
- Puppet orchestrator in the console
- Puppet orchestrator on the command line
- Puppet orchestrator API
Managing and deploying Puppet code
- Managing and deploying Puppet code
- Managing environments with a control repository
- Managing environment content with Puppetfiles
- Code Manager
- r10k
- About file sync
Provisioning with Razor
- Bare-metal provisioning with Razor
- Setting up a Razor environment
- Installing Razor
- Using the Razor client
  - Razor client commands
- Protecting existing nodes
- Provisioning a node
- Provisioning a Windows node
- Provisioning with custom facts
- Working with Razor objects
- Using the Razor API
  - API reference
- Upgrading Razor
- Uninstalling Razor
SSL and certificates
- Complete PE cert regeneration
  - Regenerating certs: mono
  - Regenerating certs: splits
- Individual PE component cert regeneration
- Regenerating a Puppet agent certificate
- Regenerating a compile master certificate
- Using an external certificate authority with PE
- Configuring the PE console to use a custom SSL certificate
- Custom Diffie-Hellman param file generation
- SSL for PE and external PostgreSQL
- Disable TLSV1 in PE
APIs
- Index of Puppet APIs
Managing MCollective
- Overview
- Invoking actions
- Controlling Puppet
- List of built-in actions
- Adding new actions
- Configuring MCollective
Maintenance
- PE database maintenance
- Back up and restore PE
Troubleshooting
- Troubleshooting the installer
- Troubleshooting connections
- Troubleshooting Code Manager
- Troubleshooting the databases
- Troubleshooting Puppet core
- Troubleshooting MCollective
- Troubleshooting Windows
Appendix
- Compliance alternate workflow

This section describes known issues in the latest Puppet Enterprise (PE) release.

Known issues are grouped by components, features, or tasks.

Installation and upgrade
Supported platforms
Console and console services
Puppet Server
PuppetDB and PostgreSQL
Puppet agent
Orchestration services
PE services and Puppet core
Razor
Code management: Code manager, r10k, and file sync
UTF-8
High availability

Tip: The known issues for Puppet Server, PuppetDB, and Puppet core link to additional release notes for the versions of those components included in this PE release.

For more information about this release, see: