Project

General

Profile

Bug #14209

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

Added by Vincent MEMBRÉ 10 months ago. Updated about 1 month ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
100
Tags:

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

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

Has duplicate Rudder - Bug #14707: Impossible to recreate a node deletedRejectedActions

Associated revisions

Revision 188b2f2e (diff)
Added by François ARMAND about 2 months ago

Fixes #14209: Impossible to reset the status of a Node using rudder-keys cli

History

#1

Updated by Alexis MOUSSET 10 months ago

  • Target version changed from 4.1.19 to 4.1.20
#2

Updated by François ARMAND 9 months ago

  • Target version changed from 4.1.20 to 4.1.21
#3

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.21 to 4.1.22
#4

Updated by François ARMAND 6 months ago

  • Related to Bug #14707: Impossible to recreate a node deleted added
#5

Updated by François ARMAND 6 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

#7

Updated by François ARMAND 6 months ago

  • Tags 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.

#8

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 5.0.10 to 5.0.11
#9

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 5.0.11 to 5.0.12
#10

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 5.0.12 to 5.0.13
  • Priority changed from 108 to 105
#11

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 105 to 102
#12

Updated by François ARMAND about 2 months ago

  • Status changed from New to In progress
  • Priority changed from 102 to 101
#13

Updated by François ARMAND about 2 months 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
#14

Updated by François ARMAND about 2 months ago

  • Related to deleted (Bug #14707: Impossible to recreate a node deleted)
#15

Updated by François ARMAND about 2 months ago

  • Has duplicate Bug #14707: Impossible to recreate a node deleted added
#16

Updated by François ARMAND about 2 months ago

  • Status changed from Pending technical review to Pending release
#17

Updated by Vincent MEMBRÉ about 1 month ago

  • Priority changed from 101 to 100
#21

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.14 which was released today.

Also available in: Atom PDF