Project

General

Profile

Actions

Bug #26325

open

Resolved properties conflicts still appear as errors in status

Added by Nicolas CHARLES 16 days ago. Updated 9 days ago.

Status:
Pending technical review
Priority:
1 (highest)
Category:
Web - Nodes & inventories
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
137
Name check:
To do
Fix check:
To do
Regression:
Yes

Description

I have 2 groups, defining String properties:
  • All debians define dns_server = 1.1.1.1
  • Production servers defines dns_server = 9.9.9.9

So i created a group to order

and the policy generation fails
UPDATE: the policy generation works, but the error saying that there is an group overridding error is not cleared when the conflict is resolved

The error message tells me to do exactly what I am doing
UPDATE: because the error message is not correctly cleared on conflict resolution


Files


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #25528: List node with properties inheritance error in status bar for generationReleasedFrançois ARMANDActions
Actions #1

Updated by Clark ANDRIANASOLO 16 days ago

  • Related to Bug #25528: List node with properties inheritance error in status bar for generation added
Actions #2

Updated by François ARMAND 16 days ago

  • Description updated (diff)
  • Severity changed from Critical - prevents main use of Rudder | no workaround | data loss | security to Minor - inconvenience | misleading | easy workaround
  • Priority changed from 180 to 137

So, after further investigation, the problem is not about blocking generation, but about correctly clearing the conflict error message when the conflict is resolved.

I double checked, and:
- the generation is correctly finished (as we can see in the given screenshot in top post, the generation part has a green check)
- nodes properties.d/properties.json contains the correct variable's value resolved by overridding.

I changed the severity to "misleading" accordingly.

Actions #3

Updated by François ARMAND 10 days ago

  • Assignee set to Clark ANDRIANASOLO
Actions #4

Updated by Clark ANDRIANASOLO 10 days ago

  • Subject changed from Properties override in groups with ordering does not work anymore on 8.2.4 to Resolved properties conflicts still appear as errors in status

As mentioned above, the conflict is resolved in generated policies, and this is a display problem : the errors should be resolved in the cached properties, and not show in "Group properties errors"

Actions #5

Updated by Clark ANDRIANASOLO 10 days ago

  • Status changed from New to In progress

Updated by Clark ANDRIANASOLO 10 days ago

The property is not also displayed in the resolving parent group, but it should.

Example for a test property, overriden with foo and bar and resolved with a group with ordering Foo, Bar :

Actions #7

Updated by Clark ANDRIANASOLO 9 days 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/6179
Actions

Also available in: Atom PDF