Issue #9681 has been updated by Jeff McCune. Status changed from In Topic Branch Pending Merge to Merged - Pending Release
# Merged into master # As: https://github.com/puppetlabs/puppetlabs-cloud-provisioner/commit/e05488704cadad2309b0fb3832f618d96ccc8091 ---------------------------------------- Bug #9681: fail explicitly if the specified group does not exist https://projects.puppetlabs.com/issues/9681 Author: Dan Bode Status: Merged - Pending Release Priority: Normal Assignee: Category: cloudpack Target version: Keywords: Branch: https://github.com/puppetlabs/puppetlabs-cloud-provisioner/pull/18 Currently, the following message is supplied when a non-existent group is specified using the classify action: <pre> puppet node classify --report_server rhel-55-64-1 --report_port 3000 foo3 --node-group does_not_exist notice: Registering node ... notice: Registering node ... Done notice: Classifying node ... warning: Classifying node ... Failed warning: Server responded with a 422 status </pre> it would be better to explicitly check if the group exists and fail with a message indicate that the group does not exist. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
