Resolve a “no parameter named” error when using custom resource types or legacy custom functions in Puppet Enterprise modules

You get a no parameter named error when using custom resource types or legacy custom functions in modules during a Puppet run.

Error messages

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named [PARAMETER NAME]

You get this error when you have different versions of the same resource type in different environments: the resource type leaks between your environments.

Version and installation information

PE version: All supported

Solution

Use environment isolation to prevent resource types from leaking between environments. To enable environment isolation, use the steps in our documentation.

To avoid plug-in conflicts for resource types, use the puppet generate types command.