Bug #25526
Updated by Clark ANDRIANASOLO about 2 months ago
A run in the policy generation may be expected to include latest changes in configuration management parts of Rudder : techniques, node properties et dynamic groups. The policy generation can fail, which results in a red error status icon in Rudder : !image%281%29.png! !https://prod-files-secure.s3.us-west-2.amazonaws.com/9095c45d-6b05-4005-a523-dd7b69d8aa7f/ee2ba2b1-f7e4-469d-b5dc-ee93bf7e350c/image.png! But some configuration management changes may break, without changing the status of the policy generation. Currently we have the knowledge that it happens for : * an inheritance conflict on groups when resolving node properties * a failed technique compilation In such case the errors are only visible in the groups or technique pages, however the user would not know from a green status icon for policy generation that such errors exist and that the generated policies are not therefore the one they expect. We should make the errors visible along the policy generation status, and adapt the meaning of the status so that such configuration errors are still always visible to users.