Project

General

Profile

Bug #5322

When a node changes its policy server, the groups hasPolicyServer are never updated, and so the promises never make their way to them

Added by Nicolas CHARLES over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
1
Category:
Server components
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

If we change the policy server of a node, like from root to another, and generate an inventory, the inventory does go to the policy server
In the web interface, the node has its policy server updated. However, the groups hasPolicyServer-uuid-of-policy-server are never updated (both root and the new one), so the generated promises do not contains all the relevant information.

We'd need to update this information (maybe as part of the dynamic group update)


Subtasks

Bug #5695: script to update a node to relay should create a dynamic groupReleased2014-10-27Benoît PECCATTEActions
Bug #5696: Add description for dynamic groups system checkReleased2014-10-27Nicolas CHARLESActions
Bug #5748: When installing a rudder server, directive common is not applied on policy serversReleased2014-11-06Nicolas CHARLESActions
Bug #5749: node-to-relay script is not correctReleased2014-11-06Vincent MEMBRÉActions
#1

Updated by Nicolas PERRON over 5 years ago

  • Target version changed from 2.10.4 to 2.6.18
#2

Updated by Nicolas PERRON over 5 years ago

  • Target version changed from 2.6.18 to 2.10.5
#3

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.5 to 2.10.6
#4

Updated by Matthieu CERDA over 5 years ago

  • Target version changed from 2.10.6 to 2.10.7
#5

Updated by Nicolas CHARLES over 5 years ago

  • Assignee set to François ARMAND

Francois,

What do you think would be the best solution ? I'm thinking that it could be a post modification hook of the received invnetory (but can we add hooks regarding groups?) or dynamic groups updates

#6

Updated by François ARMAND over 5 years ago

Not a post hook, because inventory does not have any idea about configuration.

So yes, a dynamic group seems the best way forward.

#7

Updated by François ARMAND over 5 years ago

  • Status changed from New to Discussion
  • Assignee changed from François ARMAND to Nicolas CHARLES
#8

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Priority changed from N/A to 2
  • Pull Request set to https://github.com/Normation/rudder/pull/640

Need to test it deeper, but PR is here: https://github.com/Normation/rudder/pull/640

I also found another way, but that could be used in a new "minor" version

"haspolicyServer" groups can be set to dynamic and add them a Query so we would not have to maintain a specific behavior for those groups

#9

Updated by Vincent MEMBRÉ over 5 years ago

I tested it and it works fine!

PR here: https://github.com/Normation/rudder/pull/640

#10

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
#12

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.7 and 2.11.4, which were released today.

Also available in: Atom PDF