Project

General

Profile

Actions

Bug #14209

closed

Impossible to reset the status of a Node using rudder-keys cli

Added by Vincent MEMBRÉ about 5 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
98
Name check:
Reviewed
Fix check:
Error - Fixed
Regression:

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)


Subtasks 2 (0 open2 closed)

Bug #14871: Rudder command to reset agent key/certificate RejectedBenoît PECCATTEActions
Bug #15900: /opt/rudder/bin/rudder-keys reset-status need a pubkey ReleasedBenoît PECCATTEActions

Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #14707: Impossible to recreate a node deletedRejectedFrançois ARMANDActions
Actions

Also available in: Atom PDF