Project

General

Profile

Actions

Bug #25528

closed

Bug #25526: Configuration errors should be added to policy generation status detail

List node with properties inheritance error in status bar for generation

Added by Clark ANDRIANASOLO 11 months ago. Updated 10 months ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

We have a cache of node properties since #25219 and it leads to silent error behavior when there is a conflict in the hierarchy of properties inheritance : the cache is simply not updated and when Rudder restarts the cache even remains completely empty.

We need to improve the visibility of inheritance errors by :
  • adding logs (there are no logs at all after changing the configuration of groups, unless Rudder is restarted)
  • isolating individual errors on properties to group them by node, an error on a single node property should not affect all nodes in Rudder
  • displaying the errors for every node in the status bar next to policy generation, and turn the status icon to red if there is any error
  • displaying the errors in the node and group page in the property table in the corresponding row

We should update the cache of node properties at any place where a change in the status of resolution of node properties for one or many node could occur.


Subtasks 3 (0 open3 closed)

Bug #25592: Add node property errors in inherited properties APIReleasedFrançois ARMANDActions
Bug #25632: Resolved properties need more tests and logging for success valuesReleasedFrançois ARMANDActions
Bug #25610: Display properties errors in nodes and groups pageReleasedFrançois ARMANDActions

Related issues 6 (0 open6 closed)

Related to Rudder - Bug #25530: Group properties wrongly appear empty when group has no member nodesReleasedFrançois ARMANDActions
Related to Rudder - Bug #25533: Group properties inheritance issue : Property modified for a group do not appear changed if another group defines the same property for one node both have in common.ResolvedActions
Related to Rudder - Bug #22077: Group properties web page of a group of groups containing conflicting properties are unaccessibleResolvedFrançois ARMANDActions
Related to Rudder - Bug #25332: When changing node properties the old table is sometimes still displayedReleasedFrançois ARMANDActions
Related to Rudder - Bug #26325: Resolved properties conflicts still appear as errors in status ReleasedFrançois ARMANDActions
Has duplicate Rudder - Bug #25336: Inheritance errors in properties but policy generation succeeds and properties are not loadedResolvedActions
Actions #1

Updated by Clark ANDRIANASOLO 11 months ago

  • Related to Bug #25530: Group properties wrongly appear empty when group has no member nodes added
Actions #2

Updated by Clark ANDRIANASOLO 11 months ago

#25530 is a symptom of having silent errors and fetching no group properties because the cache is empty in case of any property inheritance errors

Actions #3

Updated by Clark ANDRIANASOLO 11 months ago

  • Description updated (diff)
Actions #4

Updated by Michel BOUISSOU 11 months ago

  • Related to Bug #25533: Group properties inheritance issue : Property modified for a group do not appear changed if another group defines the same property for one node both have in common. added
Actions #5

Updated by Clark ANDRIANASOLO 10 months ago

  • Status changed from New to In progress
Actions #9

Updated by Clark ANDRIANASOLO 10 months ago

  • Subtask #25592 added
Actions #10

Updated by Clark ANDRIANASOLO 10 months ago

  • Related to Bug #22077: Group properties web page of a group of groups containing conflicting properties are unaccessible added
Actions #11

Updated by Clark ANDRIANASOLO 10 months ago

  • Subtask #25610 added
Actions #12

Updated by Clark ANDRIANASOLO 10 months ago

  • Related to Bug #25332: When changing node properties the old table is sometimes still displayed added
Actions #13

Updated by Clark ANDRIANASOLO 10 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/5921
Actions #14

Updated by Clark ANDRIANASOLO 10 months ago

  • Status changed from Pending technical review to Pending release
Actions #15

Updated by François ARMAND 10 months ago

  • Has duplicate Bug #25336: Inheritance errors in properties but policy generation succeeds and properties are not loaded added
Actions #16

Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released

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

Actions #17

Updated by Clark ANDRIANASOLO 6 months ago

  • Related to Bug #26325: Resolved properties conflicts still appear as errors in status added
Actions

Also available in: Atom PDF