Jira (PUP-11171) "Server Error: no parameter named 'max_files'", when adding max_files to file resource

1 view
Skip to first unread message

Dirk Heinrichs (Jira)

unread,
Jul 21, 2021, 3:20:04 AM7/21/21
to puppe...@googlegroups.com
Dirk Heinrichs created an issue
 
Puppet / Bug PUP-11171
"Server Error: no parameter named 'max_files'", when adding max_files to file resource
Issue Type: Bug Bug
Affects Versions: PUP 6.23.0
Assignee: Unassigned
Components: Types and Providers
Created: 2021/07/21 12:19 AM
Environment:

Linux

Priority: Major Major
Reporter: Dirk Heinrichs

Puppet Version: 6.23.0
Puppet Server Version: 6.15.3
OS Name/Version: Debian 10 (Master), Ubuntu 20.04.2 LTS (Agent)

After getting the following warning:

The directory 'XXX' contains 1530 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees

for a file resource that removes a directory tree, I added a "max_files => 2000" attribute to that resource. But then I got this:

Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'max_files' (file: /etc/puppetlabs/code/environments/production/modules/XXX/manifests/XXX.pp, line: 8) on File[XXX] (file: /etc/puppetlabs/code/environments/production/modules/XXX/manifests/XXX.pp, line: 8) on node XXX

Desired Behavior:

File resource should work as documented, catalog should be executed

Actual Behavior:

See above

BTW: Please update drop down lists for "Agent OS" and "Master OS" above. They're way outdated.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo

Gabriel Nagy (Jira)

unread,
Jul 21, 2021, 5:37:02 AM7/21/21
to puppe...@googlegroups.com
Gabriel Nagy commented on Bug PUP-11171
 
Re: "Server Error: no parameter named 'max_files'", when adding max_files to file resource

Hi Dirk Heinrichs,

My assumption is that this happens because the agent version on your primary server (which handles the catalog compilation) is older and doesn't have the max_files feature. That work (PUP-10946) went in 6.23.0 so it's available on the agent, which is why you're seeing the warning. Can you confirm that this is the case?

To be able to set the parameter in the manifest you need at least Puppet 6.23.0 on your server node.

Josh Cooper (Jira)

unread,
Jul 22, 2021, 8:17:03 PM7/22/21
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-11171

Also make sure to restart the puppetserver after upgrading its local puppet-agent package.

Dirk Heinrichs (Jira)

unread,
Jul 23, 2021, 1:52:05 AM7/23/21
to puppe...@googlegroups.com

Josh Cooper, yes, by the time this happened, the agent version on the server was still at 6.22.1, while all other agents had already been upgraded to 6.23.0. Meanwhile, everything was upgraded to 6.24.0, so I'll test again...

Dirk Heinrichs (Jira)

unread,
Jul 27, 2021, 3:59:03 AM7/27/21
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages