Bug #10453: Error during policy generation - Rudder - Issue Tracker

Actions

Copy link

Bug #10453

closed

Error during policy generation

Added by Nicolas CHARLES almost 8 years ago. Updated almost 8 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Web - Config management

Target version:

4.1.0

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

First impressions of Rudder

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

[2017-03-17 10:38:37] DEBUG com.normation.rudder.services.policies.PromiseGenerationServiceImpl - Node contexts built in 3257 ms, start to build new node configurations.
[2017-03-17 10:38:37] ERROR historization - Error with update nodes historization process <- Could not update the nodes historization information in base. <- null
[2017-03-17 10:38:37] ERROR historization - Root cause was: null
[2017-03-17 10:38:37] DEBUG com.normation.rudder.services.policies.PromiseGenerationServiceImpl - Policy generation completed in 90820 ms
[2017-03-17 10:38:37] ERROR com.normation.rudder.batch.AsyncDeploymentAgent$DeployerAgent - Error when updating policy, reason Could not update the nodes historization information in base. <- null
[2017-03-17 10:38:37] DEBUG com.normation.rudder.batch.AsyncDeploymentAgent - Flag file '/opt/rudder/etc/policy-update-running' successfully removed

Hitting "update policies" solves the issue

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES almost 8 years ago

This happens only when we didn't use much the web interface
clicking immediatly on "Update policies" doesn't fix it, but going to node list, rules, dashboard, and again clicking it fixes the issue
Something lazy is not correctly loaded

Actions

Copy link