The Puppet Labs Issue Tracker has Moved:

Bug #9679

Bug #9675: ensure that classify action works for cloud provisioner

classify action should check if node already exist and provide a clear message

Added by Dan Bode over 3 years ago. Updated about 1 year ago.

Status:Merged - Pending ReleaseStart date:09/26/2011
Priority:NormalDue date:
Assignee:Dan Bode% Done:


Category:cloud provisioner
Target version:-
Keywords: cloud_provisioner Affected URL:
Branch: Affected PE version:

We've Moved!

Ticket tracking is now hosted in JIRA:

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.


The classify action should check to see if the node_name already exists before attempting to create the node in the dashboard. If the node already exists, it should notify the user with a reasonable message.

It currently tries to recreate the node even if it already exists and provides the following unclear warning:

puppet node classify --report_server rhel-55-64-1 --report_port 3000 foo --debug --node-group test --trace
info: Using http://rhel-55-64-1:3000 as Dashboard.
notice: Registering node ...
warning: Registering node ... Failed
warning: Server responded with a 422 status
notice: Classifying node ...
notice: Classifying node ... Done


#1 Updated by Dan Bode over 3 years ago

  • Status changed from Investigating to In Topic Branch Pending Review
  • Assignee set to Dan Bode
  • Branch set to

#2 Updated by Jeff McCune over 3 years ago

  • Status changed from In Topic Branch Pending Review to Merged - Pending Release
  • Target version set to CK

#3 Updated by Kenn Hussey about 1 year ago

  • Category set to cloud provisioner

Also available in: Atom PDF