Project

General

Profile

Actions

Bug #8045

closed

Using Rudder server 3.x + rudder agent 2.11.x, a node doesn't properly detect its change of relay server

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

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

in #2443 we introduced a change for storing policy server uuid (was in /var/rudder/tmp/uuid.txt in 2.11, changed in 3.0)
The Fusion Inventory in Rudder 2.11 still uses this path however, even if promises are 3.0 (so not updated)

If a 2.11 node, which had a 2.11 Rudde server, now has a 3.0 server, the file /var/rudder/tmp/uuid.txt will never be updated
So even if the promises set the correct uuid in the rudder extension, the fusion inventory one prevails and will never be updated

Erasing the /var/rudder/tmp/uuid.txt solves the issue

So, in Rudder 3.0 tehcnique, we should purge this file if it exists


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #2443: Policy Server UUID in /var/rudder/tmpReleasedNicolas CHARLES2014-12-17Actions
Related to Rudder - Bug #9841: Error parsing inventoryReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF