Bug #17160: On high load after a reboot, generation fails because scale-out-relay not OK - Scale-out relay - Issue Tracker

Actions

Copy link

Bug #17160

closed

On high load after a reboot, generation fails because scale-out-relay not OK

Added by François ARMAND about 4 years ago. Updated almost 4 years ago.

Status:

Released

Priority:

N/A

Assignee:

Nicolas CHARLES

Target version:

5.0-1.3

Pull Request:

https://github.com/Normation/rudder-p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

To do

Fix check:

To do

Regression:

Description

We saw on a user with high load that just after a reboot, the generation fails b/c "missing scale out relay" even if the plugin was correclty loaded and licence is OK, and even if the plugin loading happens tens of minutes earlier.

Example:

[2020-04-17 00:02:21] INFO  application.plugin - Initializing plugin 'rudder-plugin-scale-out-relay': 5.0-1.2.0
[2020-04-17 00:02:21] INFO  application - Application Rudder started
// HERE: 10 minutes latter //
[2020-04-17 00:12:48] INFO  application.plugin - Plugin 'rudder-plugin-scale-out-relay' has a license and the license signature is valid.
[2020-04-17 00:12:48] ERROR com.normation.rudder.services.policies.ParallelSequence - Failure in boxToEither: Error when calculating configuration for node 'xxxx' (xxxx) <- Error for node 'xxxx' bundle creation <- We could not generate policies for server 'xxxx', therefore making updates for nodes behind it unavailable. Maybe you are missing 'scale out' plugin?