Rudder

I think I agree with the qualification.
I'm not sure where the error message should go, but clearly, we have to provide the user with a way to get out of that situation (without relying on any LDAP/cmd line wizardry).

The very first step seems to let the promise generation process runs even in that case. We could for example disable directives with broken techniques.

The second step is to allow to delete the directive. Migration would be nice but may be more difficult.

The good news it that there is a simple workaround: just revert the commit that removed the Technique, then reload Techniques library, then delete Directives based on the Technique, the delete back the Technique.

I lowered the priority to 4 because 1/ it is not a really frequent use case and 2/ the workaround is simple.

The proposed change allows to delete a Directive when no version of the technique is availabe at all:

When at least one version of the technique is available, a migration towards it is done with that warning message:

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

Applied in changeset rudder|38b1ef273d59e4b0d051ed4e4d2f9441026061f0.

This bug has been fixed in Rudder 3.1.24, 4.1.8 and 4.2.1 which were released today.

• 3.1.24: Announce Changelog
• 4.1.8: Announce Changelog
• 4.2.1: Announce Changelog
• Download: https://www.rudder-project.org/site/get-rudder/downloads/