Console and console services known issues

The known issues in this release for the console and console services are described.

Infra Assistant timeouts on the PE console

The Infra Assistant times out on the PE console. As a workaround:

The parameter puppet_enterprise::console_services socket_timeout can be set via Hiera or by configuring the data. A value of 0 removes the timeout entirely, otherwise the value is in milliseconds and defaults to 60 seconds.

Enabling the MCP server may fail if parameters are set via the Configuration data tab in the PE console

The MCP-related class parameters are set to false by default in the PE Master and PE Console node groups. As a result, attempting to enable the MCP server by adding these parameters via Configuration data may fail.

Affected parameters:

  • puppet_enterprise::profile::master::infra_assistant_enable_mcp_server

  • puppet_enterprise::profile::console::mcp_server_proxy

As a workaround:

Enable MCP on the PE Master node group

  1. In the PE console, navigate to the PE Master node group.

  2. Select the Classes tab.

  3. Locate the puppet_enterprise::profile::master class.

  4. From the Parameter name dropdown, select infra_assistant_enable_mcp_server.

  5. Change the default value from false to true.

  6. Click Add to node group.

Enable MCP on the PE Console node group

  1. In the PE console, navigate to the PE Console node group.

  2. Select the Classes tab.

  3. Locate the puppet_enterprise::profile::console class.

  4. From the Parameter name dropdown, select mcp_server_proxy.

  5. Change the value from false to true.

  6. Click Add to node group.

  7. Run Puppet on the primary server and console nodes.

Discrepancy between the PE console and backend cron parsing

There is a known inconsistency between the cron expression parser used in the PE console and the Quartz scheduler used by the backend services.

The PE console currently relies on a client-side parser to interpret cron expressions and generate human-readable scheduling descriptions. In some cases, this parser may interpret certain Quartz cron expressions differently from the backend scheduler, which uses the Quartz library for validation and execution.

As a result, you may encounter the following behaviors:

  • Valid Quartz cron expressions may be flagged as invalid in the console.

  • Human‑readable schedule descriptions may be inaccurate or simplified for some cron expressions.

  • In rare cases, the console’s description may not match the actual schedule executed by the backend scheduler.

  • The backend scheduler is the authoritative source for cron expression validation and execution. For more information see Tutorial 6.

A future release will introduce a Quartz‑compatible cron parser in the PE console to ensure consistent behavior across the console, middleware, and backend scheduler.

Advanced Patching: Disabling Advanced Patching may briefly show a 500 error

When you disable Advanced Patching in the PE console while viewing any Advanced Patching page, you may briefly see a red 500 connection refused error banner as the service restarts. After the plan finishes running, refreshing the page clears the error and displays the correct 'Please enable Advanced Patching to use this feature' message.

In most cases, the console restart logs you out automatically. When you log back in, the console loads in the correct state.