Bug #14209
closedImpossible to reset the status of a Node using rudder-keys cli
Description
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 Alexis Mousset almost 6 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND almost 6 years ago
- Target version changed from 4.1.20 to 4.1.21
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.21 to 4.1.22
Updated by François ARMAND over 5 years ago
- Related to Bug #14707: Impossible to recreate a node deleted added
Updated by François ARMAND over 5 years 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
Updated by François ARMAND over 5 years ago
- Translation missing: en.field_tag_list set to Sponsored
- Assignee set to François ARMAND
- Target version changed from 4.1.22 to 5.0.10
- Priority changed from 77 to 108
We need an API to reset the certificat for a given node.
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.10 to 5.0.11
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.11 to 5.0.12
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
- Priority changed from 108 to 105
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 105 to 102
Updated by François ARMAND over 5 years ago
- Status changed from New to In progress
- Priority changed from 102 to 101
Updated by François ARMAND over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2464
Updated by François ARMAND over 5 years ago
- Related to deleted (Bug #14707: Impossible to recreate a node deleted)
Updated by François ARMAND over 5 years ago
- Has duplicate Bug #14707: Impossible to recreate a node deleted added
Updated by François ARMAND over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|188b2f2e74816c853d6b38572b7204c68e6c3fcb.
Updated by Vincent MEMBRÉ about 5 years ago
- Priority changed from 101 to 100
- Fix check set to To do
Updated by Nicolas CHARLES about 5 years ago
- Fix check changed from To do to Error - Fixed
Updated by Alexis Mousset about 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.14 which was released today.