Project

General

Profile

Actions

User story #14207

closed

Impossible to change keys of a Node using rudder-keys cli

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

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

rudder-keys change-key command is used to when a node has a new key pair and there cannot be identified

Main problem is that we don't use anymore the attribute we change in the cli (publicKeys) but we store the key in a json as a "securityToken" in agentName attribute

We could:

  • Set it in the correct attribute
  • unset agentName to old value and keep setting publicKey to match the update process (from old inventories)
Actions #1

Updated by Benoît PECCATTE about 5 years ago

  • Target version changed from 4.1.19 to 4.3.9
Actions #2

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
Actions #3

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1795
Actions #4

Updated by Rudder Quality Assistant about 5 years ago

  • Assignee changed from Alexis Mousset to Benoît PECCATTE
Actions #5

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from Pending technical review to Pending release
Actions #6

Updated by Alexis Mousset about 5 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.9 and 5.0.5 which were released today.
Changelog
Changelog
Actions

Also available in: Atom PDF