Project

General

Profile

Actions
Copy link

Bug #4859

closed

A policy generation may occur when nothing has changed

Added by François ARMAND almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
1
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
2.10.1
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We observe policy regeneration even when nothing changed.

This is due to a change in order of the node list in system variable (for managed nodes id and hostname) from run to run.

The relative order of the sequence is actually important so that managed (id, hostname) come at the same place.

So, we need to define a particular order for nodes, and be consistent on it from run to run.

Actions
Copy link
 #1

Updated by François ARMAND almost 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/515
Actions
Copy link
 #2

Updated by François ARMAND almost 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 10 years ago

  • Subject changed from Unwanted policy regeneration even when nothing changed to A policy generation may occur when nothing has changed
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.1, which was released today.
Check out:

Actions
Copy link

Also available in: Atom PDF