Project

General

Profile

Bug #5154

Node key not deleted after deleting a node in the web ui

Added by Lionel Le Folgoc over 5 years ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
0

Description

Hi,

After deleting a node in the rudder interface, the key is still present on the rudder server:

[root@rudderdv cfengine-community]# cf-key -s
Direction IP Name Last connection Key
Incoming 10.210.114.211 - Thu Jun 26 11:59:07 2014 MD5=eb7e3c67e39ef9a4261c70dc27d48c62
Total Entries: 1

We have to remove it manually with cf-key -r <node_ip>

Thanks.


Related issues

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

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to Discussion
  • Assignee set to Lionel Le Folgoc

Lionel,

You should not need to remove this key. Does it cause a problem ? If so, which problem ?

#2

Updated by Lionel Le Folgoc over 5 years ago

I don't remember what was the problem. Since it was a node with 2.9 agent, I guess it was again the skipidentify = false issue (like #5100). Feel free to reject the bug. Thanks.

#3

Updated by Jonathan CLARKE over 5 years ago

True, it should not cause a problem, however, it does mean we make no effort to stop a node from connecting to the server. Even if we have removed it's promises by then (have we?) this would make it much harder to debug a "mis functioning" node that is actually deleted.

We should fix this.

#4

Updated by Benoît PECCATTE almost 5 years ago

  • Category set to Web - Nodes & inventories
  • Target version set to Ideas (not version specific)
#5

Updated by Benoît PECCATTE almost 5 years ago

  • Assignee deleted (Lionel Le Folgoc)
  • Parent task set to #6363
#6

Updated by François ARMAND almost 3 years ago

  • Related to Bug #4709: When a node is deleted, its generated promises are not removed added
#7

Updated by François ARMAND almost 3 years ago

  • Related to deleted (Bug #4709: When a node is deleted, its generated promises are not removed)
#8

Updated by François ARMAND almost 3 years ago

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

Updated by François ARMAND almost 3 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 0
#10

Updated by Jonathan CLARKE almost 3 years ago

  • Status changed from Discussion to New
#11

Updated by François ARMAND almost 3 years ago

  • Priority changed from 0 to 14
#12

Updated by Benoît PECCATTE over 2 years ago

  • Priority changed from 14 to 27
#13

Updated by Benoît PECCATTE over 2 years ago

  • Priority changed from 27 to 28
#14

Updated by François ARMAND over 1 year ago

  • Assignee set to François ARMAND
  • Target version changed from Ideas (not version specific) to 4.1.17
  • Effort required set to Very Small
  • Priority changed from 28 to 0
#15

Updated by François ARMAND over 1 year ago

  • Status changed from New to In progress
#16

Updated by François ARMAND over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder/pull/2080
#17

Updated by François ARMAND over 1 year ago

  • Status changed from Pending technical review to In progress
  • Assignee changed from Benoît PECCATTE to François ARMAND
#18

Updated by François ARMAND over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request changed from https://github.com/Normation/rudder/pull/2080 to https://github.com/Normation/rudder/pull/2086
#19

Updated by Rudder Quality Assistant over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by Vincent MEMBRÉ over 1 year 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