Project

General

Profile

Actions
Copy link

Bug #3382

closed

A pristine Rudder 2.6 nightly installation fails any deployment as long as the root server did not register its own inventory

Added by Matthieu CERDA over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Nodes & inventories
Target version:
2.6.0~beta1
Pull Request:
https://github.com/Normation/ldap-inv...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

A pristine Rudder 2.6 nightly installation fails any deployment as long as the root server did not register its own inventory.

We get at first a "None.get" error, and when forcing a deployment:

[2013-03-29 09:50:12] ERROR com.normation.rudder.batch.AsyncDeploymentAgent$DeployerAgent - Error when doing deployment, reason Cannot build Rule vals <- Could not replace variables <- Error when processing rule (hasPolicyServer-root/common:1.0/common-root) with variables: Stream(OWNER User launching cfe (usually root) : ArrayBuffer(${rudder.node.admin}), ?) <- DN machineId=121E0991-CBAB-3D30-D265-EB27C9753F60,ou=Machines,ou=Pending Inventories,ou=Inventories,cn=rudder-configuration does not belong to machine inventories DN ou=Machines,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration
[2013-03-29 09:50:12] ERROR com.normation.rudder.batch.AsyncDeploymentAgent - Deployment error for process '2' at 2013/03/29 09:50:12: Cannot build Rule vals

When forcing the root server to send its own inventory, things start to work normally.

Expected result: Rudder should work even without this inventory, (with just no information in the root server inventory page)

Actions
Copy link

Also available in: Atom PDF