Rudder

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.

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"

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 :

PR https://github.com/Normation/rudder/pull/6179