Project

General

Profile

Actions
Copy link

Bug #5764

closed

List of impacted rules when accepting nodes or modifing directives is not accurate

Added by Maxime Longuet about 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
2
Assignee:
Nicolas CHARLES
Category:
Web - Nodes & inventories
Target version:
2.11.8
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In Rudder 2.11 (upgrade of 2.10)

When i'm accept new node, in the list of rules that will be applied to it, there is:

"Rudder system policy: Server roles"

Files

Pièce jointe.png (61.7 KB) Pièce jointe.png Maxime Longuet, 2014-11-11 16:15

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #6454: networks.conf missing on relay serversReleasedNicolas CHARLES2015-03-31Actions
Actions
Copy link
 #1

Updated by François ARMAND about 10 years ago

  • Description updated (diff)

Hi Maxime,

Thanks for reporting.

Actions
Copy link
 #2

Updated by François ARMAND about 10 years ago

  • Subject changed from Ruder policy server on accept new node to "Rudder system policy: Server roles" is displayed on the list of future rules of a new node
  • Category set to Web - Nodes & inventories
  • Status changed from New to 8
  • Priority changed from N/A to 2
  • Target version set to 2.11.5

So, with further investigation, it appears that the problem is "only" that the rule is displayed in the pop-up, because in fact, it is not applied to the node when accepted.

So, this is a bug of medium importance, since the workaround is quite simple (just accept the node) BUT having wrong information displayed is very, very bad.

the bug seems to be only in Rudder 2.11.

Actions
Copy link
 #3

Updated by François ARMAND about 10 years ago

  • Assignee set to François ARMAND
Actions
Copy link
 #4

Updated by François ARMAND about 10 years ago

  • Subject changed from "Rudder system policy: Server roles" is displayed on the list of future rules of a new node to List of impacted rules when accepting nodes or modifing directives is not accurate
  • Description updated (diff)

It has been reported to also happen when modifing a directive. On that case, a rule using a directive was not reported in the list of impacted rules when the directive was modified.

Actions
Copy link
 #5

Updated by François ARMAND about 10 years ago

So, it seems that there is a lot of problems in ExpectedPolicyPopup#rules:Box[Seq[Rule]] way of doing the computation.

We really need a "Give me the rules for that node" in DependencyAndDeletionService, else it will break all the time.

Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.11.5 to 2.11.6
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.11.6 to 2.11.7
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.11.7 to 2.11.8
Actions
Copy link
 #9

Updated by François ARMAND almost 10 years ago

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

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
 #12

Updated by Vincent MEMBRÉ almost 10 years ago

This bug has been fixed in Rudder 2.11.8 and 3.0.2 which were were released today.

Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 10 years ago

  • Status changed from Pending release to Released
Actions
Copy link
 #14

Updated by Nicolas CHARLES over 9 years ago

  • Related to Bug #6454: networks.conf missing on relay servers added
Actions
Copy link

Also available in: Atom PDF