Bug #9149
closed
Inventory keeps its key certified when node is deleted
Added by Vincent MEMBRÉ about 8 years ago.
Updated almost 6 years ago.
Category:
Web - Nodes & inventories
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Infrequent - complex configurations | third party integrations
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
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Related to Question #9719: Node deletes are not properly cleaned up added
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Infrequent - complex configurations | third party integrations
- Target version changed from 3.1.19 to 3.1.20
- Assignee deleted (
Vincent MEMBRÉ)
This looks related to #5154 (but I can't add it as a related ticket because Redmine says it's a circular dependency)
- Target version changed from 3.1.20 to 3.1.21
- Target version changed from 3.1.21 to 3.1.22
- Priority changed from 23 to 22
- Priority changed from 22 to 36
- Target version changed from 3.1.22 to 3.1.23
- Priority changed from 36 to 35
- Target version changed from 3.1.23 to 3.1.24
- Priority changed from 35 to 34
- Target version changed from 3.1.24 to 3.1.25
- Target version changed from 3.1.25 to 387
- Target version changed from 387 to 4.1.10
- Target version changed from 4.1.10 to 4.1.11
- Target version changed from 4.1.11 to 4.1.12
- Target version changed from 4.1.12 to 4.1.13
- Target version changed from 4.1.13 to 4.1.14
- Target version changed from 4.1.14 to 4.1.15
- Target version changed from 4.1.15 to 4.1.16
- Target version changed from 4.1.16 to 4.1.17
- 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.
- Status changed from New to In progress
- Assignee set to François ARMAND
- Target version changed from 4.3.7 to 4.1.17
Actually the part about key status did not changed.
- 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
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
Also available in: Atom
PDF