The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #15113

Auto-deactivation of stale nodes

Added by Deepak Giridharagopal about 2 years ago. Updated about 2 years ago.

Status:ClosedStart date:06/19/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:0.10.0
Keywords: Affected PuppetDB version:
Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

Numerous requests for this from users. It would be cool if we had a way to configure PuppetDB such that nodes get automatically deactivated if we haven’t received a catalog or facts or whatever from them in some user-specified grace period.

This is particularly helpful for users running in environments like EC2, where machines are often ephemeral.

History

#1 Updated by Deepak Giridharagopal about 2 years ago

  • Status changed from Unreviewed to In Topic Branch Pending Review
  • Target version set to 1.0.0

#2 Updated by Deepak Giridharagopal about 2 years ago

  • Status changed from In Topic Branch Pending Review to Merged - Pending Release

#3 Updated by Deepak Giridharagopal about 2 years ago

  • Target version changed from 1.0.0 to 0.10.0

#4 Updated by Deepak Giridharagopal about 2 years ago

  • Status changed from Merged - Pending Release to Closed

Also available in: Atom PDF