Project

General

Profile

Actions
Copy link

Bug #6039

closed

The expected reports of other rules are not correctly updated when we create a new rule

Added by Nicolas CHARLES almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
3.0.0~rc1
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I created a directive to install a package, that a applied twice on two identical rule
The result is:
- the generated promises ocntains twice the package to install
- one of the rule contains all the node in its target list
- another one does contain only one node in its target list

When drilling down in the database, the expected reports on node have the config id correct for the second rule created, but for the first one, only one out of two has the correct config id (the fact that it is first and second may be just random)

Related issues 3 (0 open — 3 closed)

Related to Rudder - Bug #5329: False "no answer" reporting when rules with "unique" directive are overriddenReleasedNicolas CHARLES2014-07-30Actions
Related to Rudder - Bug #6020: In change only mode, when a node never answered and a given directive is applied on two differents Rules, the reports in the node details show Could not fetch reports informationRejected2014-12-17Actions
Related to Rudder - User story #5296: Create the logic to get execution reports for "error only" modeReleasedNicolas CHARLES2014-09-24Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 10 years ago

If then update the directive, the list of node in the rules is corrected

Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 10 years ago

  • Subject changed from When I apply same directive twice to Node, the expected reports are not correctly updated to The expected reports of other rules are not correctly updated when we create a new rule

Ok ,the problem is more complex than that.
Simply creating a new rule to nodes will change the ocnfig id for this node, but not the expected config id of all others rules applying on these nodes. So it fails...

Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 10 years ago

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

Updated by Nicolas CHARLES almost 10 years ago

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

Updated by Vincent MEMBRÉ almost 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~rc1, which was released today.

Actions
Copy link

Also available in: Atom PDF