The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Bug #9675: ensure that classify action works for cloud provisioner
classify action should check if node already exist and provide a clear message
|Status:||Merged - Pending Release||Start date:||09/26/2011|
|Assignee:||Dan Bode||% Done:|
|Branch:||https://github.com/puppetlabs/puppetlabs-cloud-provisioner/pull/18||Affected PE version:|
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.
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
#2 Updated by Jeff McCune about 3 years ago
- Status changed from In Topic Branch Pending Review to Merged - Pending Release
- Target version set to CK