Project

General

Profile

Actions

Bug #16741

closed

Policies do not seem to be regenerated when a node change its policy server

Added by Félix DALLIDET almost 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

I had a node under my root server, I changed its policy server to a relay, sent an inventory.
The webapp showed it managed by the relay but the node itself was not able to update its policies, nor the relay was able to get them.
I had to manually retrigger a generation to make eveything work.

Still, I am not 100% sure that I just did not wait long enough for all the elements to triggers.


Related issues 1 (1 open0 closed)

Related to Rudder - Bug #16198: When switching a node managed by the root server to a relay, its policies are not regeneratedNewActions
Actions #1

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 6.0.3 to 6.0.4
Actions #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.4 to 6.0.5
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.5 to 6.0.6
Actions #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.6 to 6.0.7
Actions #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.7 to 6.0.8
Actions #6

Updated by Félix DALLIDET over 4 years ago

  • Status changed from New to Rejected

Duplicate of #16198

Actions #7

Updated by Félix DALLIDET over 4 years ago

  • Related to Bug #16198: When switching a node managed by the root server to a relay, its policies are not regenerated added
Actions

Also available in: Atom PDF