Bug #9149
closedInventory keeps its key certified when node is deleted
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
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Janos Mattyasovszky about 8 years ago
- Related to Question #9719: Node deletes are not properly cleaned up added
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Benoît PECCATTE over 7 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
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Jonathan CLARKE over 7 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)
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.21 to 3.1.22
- Priority changed from 23 to 22
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.22 to 3.1.23
- Priority changed from 36 to 35
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.23 to 3.1.24
- Priority changed from 35 to 34
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.25 to 387
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 387 to 4.1.10
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.10 to 4.1.11
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.16 to 4.1.17
Updated by François ARMAND about 6 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.
Updated by François ARMAND about 6 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 6 years ago
- Target version changed from 4.3.7 to 4.1.17
Actually the part about key status did not changed.
Updated by François ARMAND about 6 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
Updated by Rudder Quality Assistant about 6 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
Updated by François ARMAND about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|18c1a1b42201c7856d74178a7b5a38e87e4e30a5.
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from Pending release to Released