Impossible to reset the status of a Node using rudder-keys cli
If you want to invalidate a state of the key of a Node (from Certified to Unknown) to allow to change a key of a Node it's impossible.
The status is correctly unset but the algorithm on the server side still use the old key...
Something is fishy in that algorithm, I think we should not use the already saved key in that case but the inventory one (see https://github.com/Normation/ldap-inventory/blob/4.3.8/inventory-api/src/main/scala/com/normation/inventory/services/provisionning/CheckInventoryDigest.scala#L176)
Updated by François ARMAND 9 months ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Very Small
- Priority changed from 0 to 77
I'm setting it to "major", because when it happens, it's really complicated for an user to know what to do next. It may be linked to: https://issues.rudder.io/issues/14707