Project

General

Profile

Actions

Bug #9149

closed

Inventory keeps its key certified when node is deleted

Added by Vincent MEMBRÉ over 4 years ago. Updated over 2 years 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 1 (0 open1 closed)

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

Related issues

Related to Rudder - Bug #9719: Node deletes are not properly cleaned upNewActions
Actions #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #4

Updated by Janos Mattyasovszky over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #6

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #7

Updated by Benoît PECCATTE about 4 years ago

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

Updated by Benoît PECCATTE about 4 years ago

  • Priority set to 23
Actions #9

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #10

Updated by Jonathan CLARKE about 4 years ago

  • Assignee deleted (Vincent MEMBRÉ)
Actions #11

Updated by Jonathan CLARKE about 4 years ago

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

Actions #12

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #13

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.21 to 3.1.22
  • Priority changed from 23 to 22
Actions #14

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 22 to 36
Actions #15

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 36 to 35
Actions #16

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.23 to 3.1.24
  • Priority changed from 35 to 34
Actions #17

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #18

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.25 to 387
Actions #19

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 387 to 4.1.10
Actions #20

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #21

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #22

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #23

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #24

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #25

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #26

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #27

Updated by François ARMAND over 2 years 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.

Actions #28

Updated by François ARMAND over 2 years ago

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

Updated by François ARMAND over 2 years ago

  • Target version changed from 4.3.7 to 4.1.17

Actually the part about key status did not changed.

Actions #30

Updated by François ARMAND over 2 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/2082
Actions #31

Updated by Rudder Quality Assistant over 2 years ago

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

Updated by François ARMAND over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years 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
Actions

Also available in: Atom PDF