Bug #5322
closed
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 10 years ago.
Updated about 10 years ago.
Category:
Server components
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)
- Target version changed from 2.10.4 to 2.6.18
- Target version changed from 2.6.18 to 2.10.5
- Target version changed from 2.10.5 to 2.10.6
- Target version changed from 2.10.6 to 2.10.7
- 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
Not a post hook, because inventory does not have any idea about configuration.
So yes, a dynamic group seems the best way forward.
- Status changed from New to Discussion
- Assignee changed from François ARMAND to Nicolas CHARLES
- 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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- 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