Project

General

Profile

Actions

Bug #3818

closed

Wrong name used for Puppet class selection in host create

Added by Marco De Vitis about 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Category:
Foreman commands (obsolete)
Target version:
Difficulty:
Triaged:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

Description

When using "hammer host create" with the --puppet-class-ids parameter to add some Puppet classes to the new host, hammer calls the Foreman API with a "puppet_class_ids" option, but the correct option as used by the Foreman GUI is "puppetclass_ids".
This results in the hammer command line failing with "500 Internal Server Error".


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #3884: In host create/update in the apidoc there is param puppet_class_ids instead of puppetclass_ids (which is expected by the API)ClosedActions
Has duplicate Foreman - Bug #3987: Host creation with hammer fails with 500 errorDuplicate01/09/2014Actions
Actions #1

Updated by Martin Bacovsky about 10 years ago

  • Category set to Foreman commands (obsolete)
  • Status changed from New to Ready For Testing
  • Assignee set to Martin Bacovsky
  • Target version set to 1.9.3

Thanks for reporting this issue. Here is the PR https://github.com/theforeman/hammer-cli-foreman/pull/56 and the fix should land in the next hammer release.

Actions #2

Updated by Martin Bacovsky about 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Applied in changeset foreman:hammer-cli-foreman|commit:347e71aac723cfb4b085799183fece581e53ccd7.

Actions #3

Updated by Dominic Cleal about 10 years ago

  • Related to Bug #3884: In host create/update in the apidoc there is param puppet_class_ids instead of puppetclass_ids (which is expected by the API) added
Actions #4

Updated by Dominic Cleal about 10 years ago

  • Has duplicate Bug #3987: Host creation with hammer fails with 500 error added
Actions

Also available in: Atom PDF