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.

Puppet Edge tasks do not appear after system reboot

If you are using Puppet Edge and reboot your system, you will be unable to view your Edge based tasks i.e. edgeops, playbook_runner on the PE console after restarting. As a workaround, restart pe-bolt-server after rebooting your system to view your Edge tasks.

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.