Project

General

Profile

Bug #9149

Inventory keeps its key certified when node is deleted

Added by Vincent MEMBRÉ about 2 years ago. Updated 17 days ago.

Status:
Released
Priority:
1
Category:
Web - Nodes & inventories
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
34

Description

Inventory is signed with agent key in 3.1 (when node is accepted or key accepted on migrated installation)

Key can have two status:

Undefined => Inventory is pending or Inventory from old migrated node
Certified => Inventory has been accepted or Key accepted on old migrated node

But when a Node is removed, the signature keep being certified so when the node come back (same id, different key) comes back, it breaks

On a side note, check that signature file name is different for a node


Subtasks

Bug #13843: Inventory keeps its key certified when node is deleted even is keystatus is erasedReleasedFrançois ARMAND

Related issues

Related to Rudder - Bug #9719: Node deletes are not properly cleaned upNew

Associated revisions

Revision 18c1a1b4 (diff)
Added by François ARMAND about 1 month ago

Fixes #9149: Inventory keeps its key certified when node is deleted

History

#1 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.14 to 3.1.15

#2 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.15 to 3.1.16

#3 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.16 to 3.1.17

#4 Updated by Janos Mattyasovszky about 2 years ago

  • Related to Bug #9719: Node deletes are not properly cleaned up added

#5 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.17 to 3.1.18

#6 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.18 to 3.1.19

#7 Updated by Benoît PECCATTE over 1 year ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Infrequent - complex configurations | third party integrations

#8 Updated by Benoît PECCATTE over 1 year ago

  • Priority set to 23

#9 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.19 to 3.1.20

#10 Updated by Jonathan CLARKE over 1 year ago

  • Assignee deleted (Vincent MEMBRÉ)

#11 Updated by Jonathan CLARKE over 1 year ago

This looks related to #5154 (but I can't add it as a related ticket because Redmine says it's a circular dependency)

#12 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#13 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.21 to 3.1.22
  • Priority changed from 23 to 22

#14 Updated by Benoît PECCATTE over 1 year ago

  • Priority changed from 22 to 36

#15 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 36 to 35

#16 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.23 to 3.1.24
  • Priority changed from 35 to 34

#17 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.24 to 3.1.25

#18 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.25 to 387

#19 Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 387 to 4.1.10

#20 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 4.1.10 to 4.1.11

#21 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.11 to 4.1.12

#22 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.12 to 4.1.13

#23 Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 4.1.13 to 4.1.14

#24 Updated by Benoît PECCATTE 4 months ago

  • Target version changed from 4.1.14 to 4.1.15

#25 Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 4.1.15 to 4.1.16

#26 Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 4.1.16 to 4.1.17

#27 Updated by François ARMAND about 1 month ago

  • Target version changed from 4.1.17 to 4.3.7

Key certification changed a lot in rudder 4.2, correcting for 4.3 and up.

#28 Updated by François ARMAND about 1 month ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND

#29 Updated by François ARMAND about 1 month ago

  • Target version changed from 4.3.7 to 4.1.17

Actually the part about key status did not changed.

#30 Updated by François ARMAND about 1 month 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/2082

#31 Updated by Normation Quality Assistant 29 days ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND

#32 Updated by François ARMAND 29 days ago

  • Status changed from Pending technical review to Pending release

#33 Updated by Vincent MEMBRÉ 17 days ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.17, 4.3.7 and 5.0.3 which were released today.
Changelog
Changelog
Changelog

Also available in: Atom PDF