Project

General

Profile

Actions

User story #4658

closed

Option to disable a node

Added by Dennis Cabooter about 10 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

It would be nice if a node could be set in maintenance state or be set to temporary disabled. For example, I have a node that's offline for a known reason. Thats means all reports are in NoAnswer. Now in the node compliance calculation, compliancy will never be 100%.


Related issues 2 (0 open2 closed)

Has duplicate Rudder - User story #9868: Node maintenance / deactivation switchRejected2016-12-29Actions
Is duplicate of Rudder - User story #2888: Be able to disable a nodeRejectedActions
Actions #1

Updated by Nicolas CHARLES about 10 years ago

If a node is disabled, would you expect its compliance to be the last one before being disabled ?

That sounds like a great idea

Actions #2

Updated by Jonathan CLARKE about 10 years ago

Nicolas CHARLES wrote:

If a node is disabled, would you expect its compliance to be the last one before being disabled ?

No, I would expect it to be displayed as "Disabled", and not counter in total compliance for that period of time.

Actions #3

Updated by Dennis Cabooter about 10 years ago

What Jon says! :-)

Actions #4

Updated by Benoît PECCATTE almost 9 years ago

  • Category set to Web - Config management
  • Target version set to Ideas (not version specific)
Actions #5

Updated by Alexis Mousset about 7 years ago

Actions #6

Updated by Alexis Mousset about 7 years ago

Actions #7

Updated by Alexis Mousset about 7 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF