Bug #9286: node.rb timeout is too low for some usecases and not configurable - Installer - Foreman

Actions

Copy link

Bug #9286

closed

node.rb timeout is too low for some usecases and not configurable

Added by Jiri Stransky about 9 years ago. Updated almost 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

1.8.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

For some usecases catalog compilation might take a longer time, and when there's too many requests to Foreman and Passenger decides to handle the request from node.rb by a freshly spawned worker, node.rb can hit the time out, fail to send the catalog to the client, and the client's Puppet run ends with error.

The timeout is currently hardwired to 10 seconds in puppet-foreman. It should be configurable at least, and maybe raising the default should be considered (especially due to the fresh Passenger worker issue described above).

Blocks this BZ https://bugzilla.redhat.com/show_bug.cgi?id=1188704