Bug #5154: Node key not deleted after deleting a node in the web ui - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #5154

closed

User story #6363: Secure agent/server communication

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

Added by Lionel Le Folgoc over 10 years ago. Updated almost 6 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Nodes & inventories

Target version:

4.1.17

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Technique editor | Rudder settings

Effort required:

Very Small

Priority:

Name check:

Fix check:

Regression:

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 1 (0 open — 1 closed)

Related to Rudder - Question #9719: Node deletes are not properly cleaned up

Resolved

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Nicolas CHARLES over 10 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 ?

Actions

Copy link

Updated by Lionel Le Folgoc over 10 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.

Actions

Copy link

Updated by Jonathan CLARKE about 10 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.

Actions

Copy link

Updated by Benoît PECCATTE over 9 years ago

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

Actions

Copy link

Updated by Benoît PECCATTE over 9 years ago

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

Actions

Copy link

Updated by François ARMAND over 7 years ago

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

Actions

Copy link

Updated by François ARMAND over 7 years ago

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

Actions

Copy link

Updated by François ARMAND over 7 years ago

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

Actions

Copy link

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

Actions

Copy link

#10

Updated by Jonathan CLARKE over 7 years ago

Status changed from Discussion to New

Actions

Copy link

#11

Updated by François ARMAND over 7 years ago

Priority changed from 0 to 14

Actions

Copy link

#12

Updated by Benoît PECCATTE over 7 years ago

Priority changed from 14 to 27

Actions

Copy link

#13

Updated by Benoît PECCATTE about 7 years ago

Priority changed from 27 to 28

Actions

Copy link

#14

Updated by François ARMAND about 6 years 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

Actions

Copy link

#15

Updated by François ARMAND about 6 years ago

Status changed from New to In progress

Actions

Copy link

#16

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 Benoît PECCATTE
Pull Request set to https://github.com/Normation/rudder/pull/2080

PR https://github.com/Normation/rudder/pull/2080

Actions

Copy link

#17

Updated by François ARMAND about 6 years ago

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

Actions

Copy link

#18

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 changed from https://github.com/Normation/rudder/pull/2080 to https://github.com/Normation/rudder/pull/2086

PR https://github.com/Normation/rudder/pull/2086

Actions

Copy link

#19